Android

kotlin is a great programming language. The ui (compose) can also be used in kotlin multi platform to make desktop apps. You'll have to learn about lifecycles etc but it'll be worth it in my opinion

Unless you're willing to get raped by the sheer amount of google's surveillance, I'd say no You will be required to present your government ID, pay 25$ and other shit just to get a chance at getting approved and distributing your software

I'm long behind on Android development. I stopped not long after Google promoted Kotlin as the primary language for Android development. I really liked Kotlin though. Still these days, I'd probably go with react native or flutter. I always hear about people using those and see job postings for those in regards to android. I'd be interested in using Kotlin Multiplatform and hoping that builds up momentum and becomes super successful

If you want to build something fast and not deal with the ridiculous and ever-changing complexity that is Eclipse/Kotlin, consider Flutter. It's cross-platform so if there turns out to be a Linux phone that gets past the stage of novelty, you won't be re-writing it.

Flutter has it's downsides, but it's a pretty good platform overall. Many Android (and iOS) apps are done in it.

The question is really: what is your goal? You say Open Source software development - which software are you talking about? Are there certain projects you're looking at? Are you looking at starting your own project? Are you trying to move the open source ecosystem forward generally? (Also, what is your current skillset? Are you just getting into development or are you fairly experienced already in other platforms?)

If it's the first, follow the project and see what they're doing. If it's the second: look at the requirements. Most likely though, you will be stuck with Android, because the iPhone is even worse, and Linux on phones is far from being daily driver worthy for the vast majority of people. Alternatively, as people mentioned, you could try a Cross-Platform framework, but do be aware that these have downsides, as well. If it's the third: why not try to see what you can do to improve the situation of Linux on phones? Depending on what you're already capable of, you may already have the prerequisites to move that area forward, something badly needed IMO.

Oh man, I totally get you. But as others said, it is relatively easy to publish apps on the Play Store.

And I honestly think that the fight is far from over. I think it only serves Google's purpose to already admit defeat.

If not in the US (whom I believe to be highly interested in tracking down "rogue" app authors), then at least other jurisdictions might outlaw this anticompetitive behavior.

Yes.

Learning is fine. Its not too much different than other development if you have ever worked on java.

That being said if i had to make an app, i would just make a mobile site and call it a day. That way you can have iphone and any computer work with it.

These changes aren't going to prevent a developer from firing up Android studio and running their app. Distribution is where you'll encounter some speed bumps as these changes go into effect.

You can publish your open source app on Google Play, and this will not change. Google is also not planning to introduce $100/year publishing fee for devs like Apple, you pay $25 one time to register. There is also no real alternative open source OS for phones.

Google decision impacts apps like Termux, who use old Android API to install additional packages. If you are not planning to create Linux emulator, I guess this won't impact you.

I think it's still fine, especially given that non Play Store apps will still be runnable, albeit with a very stupid 24 hour waiting period if no action is taken by relevant regulatory bodies.

But if you are looking to eventually ditch Android for Linux phones, you could always try your hand at making Linux-native mobile apps!