Do you care if the app is open source? Which phone is this?
For whatever reason, even if it's not true, Google seems to want to create/preserve an image that there's this huge barrier to entry.
-
-
There really isn't much of a barrier to entry and it works fine without the IDE. They encourage people to use the IDE because it has a lower barrier to entry than using the CLI tools, which work fine alone.
-
For some really warped idea of "barrier to entry"...
-
So what barrier to entry is there to downloading https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip … from https://developer.android.com/studio/index.html … and using sdkmanager to update / install whatever you need?
-
That's a start and probably ok for lots of users (but buried and hard to find and not documented). They don't even have a link to the source anywhere I can find though.
-
Looks like big distros (e.g. Debian) might have it packaged tho, in which case you get most of the benefits of source (trusted reproducible build, compat with whatever arch you're running not just x86_64, ...).
-
Debian has packages but it's a bad idea to use those. It's important to use the up-to-date tools and it really doesn't need to be installed system-wide. Can also decide to install the IDE later and it knows how to use an existing minimal SDK directory for the tools.
-
Well where do you get the sources to build the SDK? This is all so awful and undocumented.
-
Not sure why you're talking about building it now. A hello world tutorial doesn't really start with building glibc, binutils and GCC.
- 1 more reply
New conversation -
-
-
I'd rather say there is a fairly big shift in focus from native apps to solutions like Flutter and React Native, which is allegedly easy compared to Android
-
Flutter apps are essentially native, but portable. They don't really respect platform UI guidelines but that's not really tied to whether or it's native or not. Android apps don't really get all that from the OS directly but rather the support libraries.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.