It’s funny, your comment highlights exactly why experience is important. You don’t know what you don’t know about Android development. You have a set of very basic assumptions about how the API works, and have no idea what the challenges of Android development are. Sure, you could figure out how to build a basic app quickly, but you probably wouldn’t do a good job building the foundation of a large app being worked on by dozens or hundreds of engineers.
> You don’t know what you don’t know about Android development
What’s that? If you gonna mention Java shenanigans like memory management and garbage collector, .NET is fairly close. Mobile-specific things like multi-touch UX and power management are shared by all battery-powered devices. Many kernel-specific things are shared with all Linuxes including desktop, server, and embedded.
> you probably wouldn’t do a good job building the foundation of a large app
I probably will. I already did a few times in my career. When I found that iOS development job a decade ago, I had zero prior experience with the platform. I had many years of prior experience developing stuff for Windows, game consoles, and some older mobile platforms.
