I'm currently taking a Mobile Applications course which teaches #android dev and is waaaaaay all in on #Google bullshit. I'd love some tips on how to make de-Googled apps; for instance, what APIs should I avoid to ensure that the app will work well under LineageOS and other such AOSP based systems?
@tindall It's been a couple of years since I did Android but ISTR the delineation between Android APIs and Google ones is fairly clear. And you can easily create AVDs without Google APIs for testing.
@hiemstra to expand on this, the loss of efficiency and dependency on either Chrome's broken implementation of standards is not better than being slightly limited in my capabilities as a native app.
@tindall have a look at f-droid. That is the best place to distribute Google free apps. Good idea to follow their rules.
@tindall Firebase and Google GMS (Play Services)
the separation is thankfully pretty clear and you literally interact with an object called GoogleApi
AndroidX/Support Library is fine, it's included in your app
@tindall I am no expert, but would look at https://f-droid.org/en/packages/org.fdroid.fdroid/ and what devs do to create f-droid apps!
An don't switch to the Facebook SDK. 😉
https://media.ccc.de/v/35c3-9941-how_facebook_tracks_you_on_android #f***book #35c3
@tindall Man this is hard. So what is it you're looking to do?
There's things I think about:
* Notifications (Using SSE (Server Side Events), WebSockets, polling libraries)
* Authentication (scope-control using OAuth2 + token with refreshing)
* API wrapping - meh
ｃｙｂｒｅｓｐａｃｅ: the social hub of the information superhighway
jack in to the mastodon fediverse today and surf the dataflow through our cybrepunk, slightly glitchy web portal