This is an automated archive made by the Lemmit Bot.
The original was posted on /r/androiddev by /u/DBSmiley on 2025-02-06 14:53:21+00:00.
Hey all,
I’m a CS Professor teaching a mobile dev class, and I’m teaching native Android dev and Flutter as two frameworks - I start with native dev, then look at multiplatform dev with Flutter (though considering switching to KMP for cross-platform, but I kind of like that there’s a paradigm shift between Android and Flutter).
Specifically on native Android dev, I find paradigms change quickly. Hell, when I first taught it, I was using Java with XML layouts (don’t worry, I’m using Compose - Kotlin is the bestest language ever). I only teach this class once a year, and unfortunately I just don’t have the time/space to practice “real” Android development at scale since I typically have 4 courses with an average of 200+ students a year. I try to teach the best practices I see
When I looked a year ago, most places I saw said something akin to “Navigation sucks, I still use Intents and multiple-activities”, but more and more tutorials and dev videos I see seem to be using Navigation these days.
My question is, if you, knowing what you know now, which would you generally encourage newer developers to focus on?
-
“Activity per screen” + Intent-driven navigation
-
Navigation with Single Activity Architecture
Which would you generally recommend now? I end up covering intents anyways with Services/Intent-filters, etc. but within an single application with multiple “screens”, which would you generally recommend teaching?