> Some devs say one Activity for the whole app and just swap fragments!
Meaning pick and choose what you want to do. If you're writing a game, this is probably the way to go.
If you're writing a form entry application with a million controls, fragments fragments fragments. Did I mention fragments should be used here ?
You forgot to mention that there are devs saying many other things. Use C++/Qt. Use unity. Use C#. Use ... your choice !
> The Android SDK is loaded with tons of components with unfriendly APIs
Sounds way better than javascript, where you have 5 different API's, you have to support at least 3 of them, none of them are equal, they have bugs that will never be fixed, and they are yanked from under your feet every 2 years or so. Oh and that's ignoring that basic things are still completely impossible.
> Do people actually use any of this stuff still or is this blog post from 2008 with no code formatting really the best resource?
Sounds like it's got the javascript documentation beat by a wide margin.
Meaning pick and choose what you want to do. If you're writing a game, this is probably the way to go.
If you're writing a form entry application with a million controls, fragments fragments fragments. Did I mention fragments should be used here ?
You forgot to mention that there are devs saying many other things. Use C++/Qt. Use unity. Use C#. Use ... your choice !
> The Android SDK is loaded with tons of components with unfriendly APIs
Sounds way better than javascript, where you have 5 different API's, you have to support at least 3 of them, none of them are equal, they have bugs that will never be fixed, and they are yanked from under your feet every 2 years or so. Oh and that's ignoring that basic things are still completely impossible.
> Do people actually use any of this stuff still or is this blog post from 2008 with no code formatting really the best resource?
Sounds like it's got the javascript documentation beat by a wide margin.