Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
AleCx0415689218dMakes you wonder how some people did it eh?
I worked on android and ios for 2 years, fucking hated every second of it. 300+ lines just to get a permission and shit. Thing is bs.
Background services through the broadcast reciever is a fucking hack, and if you don't watch out shit will get rejected in the Android store either way.
Not a clue. Btw people at so don't know how to do it either.
We all fucked in this mofocka
JoshBent27145218d>>because background services are deprecated<<
What did they get replaced with? also it sounds like you're developing some sort of internal app, just have a notification up, so your app doesn't get killed?
TitanLannister3684217d@JoshBent apparently they got replaced by job schedulers which are absolutely different. using background services were so easy : just start it on first launch and forget about it.everything under app's control.
With job schedulers , everything is in the hands of system , whenever it has its resources free , then only it will run.
Now a message comes at 2pm , and schedular wakes my app at 4 pm , then what's the point ?
and about that foreground notification: yeah , i won't mind that. But it seems to get killed too! and weirdly enough, whenever the reciever recieves a message , it gets killed :?/
Haxk2032991217dYou want more security but you want to make the coding easy as possible ? Hahaha. Thats not going to happen.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job