Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
Android dev of many many many years here.
Android Studio with Jetpack Compose.
I'd also suggest you try doing kotlin multiplatform. You can take your Android app and end up with a iOS app, and if you want, a desktop app. You would need a Mac for the ios app eventually, but not for the desktop apps.
There is minimal work to get it set up to start, they provide a wizard, and there are a lot of libraries available now that are multiplatform.
IOS and Desktop are both considered stable now, but the iOS beta was pretty solid.
All the apps it generates are native apps.
Even if you don't want to do multiplatform to start, if you use kotlkn only libraries that are capable of it, you could easily switch to it in the future if you wanted to as it'd be structured properly from the start.
E.g for libraries if you use Koin instead of Dagger2/hilt you could switch to multiplatform in the future without much effort. If you chose dagger instead, it'd be a big task to switch. And if you start it as multiplatform but Android only, you'll know which areas still need implementation work later to eventually work on iOS.