android - Service connecting to Firebase a bad idea? -



android - Service connecting to Firebase a bad idea? -

i building android app requires real time updates. server firebase. firebase meant receive updated info when user connected server. impressed firebase far, concern receiving new info when app not active. not want seek these ideas find out bad idea, short on time. looking suggestions , advice.

a service (example). worried battery consumption , going on connection limit if users connected. an alarmmanager run sync every x hours. worried not getting updates enough. using gcm force notification send tickle. worried paying service.

any other suggestions or possible issues missed? time!

edit

i found this thread. still unsure. maybe service not bad idea, per james tamplin (suspect firebase dev)

you want utilize gcm in these situations.

firebase works fine background service, leaves socket open, it's going utilize quite bit of power. powerfulness usage fine when user actively engaged app (the screen uses lot more), when it's running in background, it's going hard on battery life.

in cases, when user isn't actively engaged, they're willing take slower response times, , force services gcm improve value in watts per user happiness.

also, firebase working on adding triggers, demonstrated in this video google cloud platform live, create lot easier integrate force services gcm in future.

and guess james firebase dev. he's 1 of co-founders :)

android database firebase

Comments

Popular posts from this blog

php - Edges appear in image after resizing -

ios8 - iOS custom keyboard - preserve state between appearances -

Delphi change the assembly code of a running process -