Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Android development is just so fucking obnoxiously complex man
I would say Android was specifically designed to make big thinks work, but doesn't care about small ones.
The separation in e.g. Activities for Foreground, Services for Background are useful for larger projects, as they enforce this separation by Design. For simple things, this overly complicates everything, when not even necessary. On the other hand "going bigger" is easier then.
I know your pain.
Fuck Android's life cycle!
Xamarin Forms makes Android apps run in a single Activity and sets it to keep alive on rotation just to avoid most of the bullshit.
arte921111yWhy does Google have to do every android api in the most complex way
I feel your pain. I have realised that if an app requires a lot of cloud data handling and making internet requests, then having pwa or other non native option is the best. Native framework has yet to figure out better ways for dealing with the internet.
Although if you want to make a data requests that could take upto 15 seconds, then foreground service with a notification might be a the most valid solution. Other options in no particular order would be job schedular/work manager , retrofit+okhttp / volley / other network handling library
Also, asynctask was/is shit and now deprecated. And dealing with threads also don't give much better results. So try to stay away from them
@StopWastingTime AFAIK a lot of the new APIs (including JobIntent, from reading my error stacks!) Use AsyncTask under the hood.