Thanks for asking - this is a fairly common challenge, and hard to handle perfectly.
It's simple to monitor connectivity, and see what type of connectivity the user has, using libraries or system reachability APIs.
On iOS, the system is the arbiter - you can read the network conditions, and tell certain requests (like large downloads) to only happen via WiFi, but you can't force a request to go via cellular. Android has some more flexibility in this regard, but I'm not familiar with the best practices.
So how do you deal with low wifi signal? do you force it to go on mobile network?
Thanks for asking - this is a fairly common challenge, and hard to handle perfectly.
It's simple to monitor connectivity, and see what type of connectivity the user has, using libraries or system reachability APIs.
On iOS, the system is the arbiter - you can read the network conditions, and tell certain requests (like large downloads) to only happen via WiFi, but you can't force a request to go via cellular. Android has some more flexibility in this regard, but I'm not familiar with the best practices.
Nah mobile dev is actually easy. If you use Flubber, not the deprecated Android/iOS native.
Backend is pretty easy if you use excel
Lol..exactly...hater's gonna hate, my friend. Thanks for the nice article, we native mobile devs really deserves some consideration.