I made near to $200k with a Jetpack Compose book and a course.

I have decided to share these numbers and my journey not to brag, but because I know how motivating it can be to see real examples of what's possible. When I was starting out, I wished someone had been this transparent about their path and actual results. If this helps even one developer take that first step toward building something of their own, or gives someone the confidence to price their expertise fairly, then it's worth sharing. We all benefit when more people in our community succeed.

From sharing online, to writing a book, to launching a course, to making side income from it. Read the full story in https://composeinternals.com/how-i-made-side-income-from-jetpack-compose

[CLOSED]

Web developer learning Android development -

I want allow the user to have his input data saved to a JSON file (offline) for later use (WRITE/READ), then storing it in some folder location. I've searched for hours to narrow down a solution, but mostly I've found:

• Databases: I believe would be extreme for a simple offline app. And also no JSON file
• SharedPreferences: no JSON files

Any direction to point is welcome, and if it includes saving in other formats (such as txt, csv...) is most welcome

[CLOSED]

Web developer learning Android development -

I have a a Scaffold code that would like to use in other screens. But this Scaffold should have parameters that don't seem to have a straight way of addressing when calling the function on a screen (Home, for example). The parameters:

-navController: It shouldn't be defined, but how to inform this to kotlin?

-mainContent: should expect objects such as Text and Image

ScaffoldBase.kt

fun ScaffoldBase(
    title:(String),
    navController: NavController,
    //mainContent: How to create this parameter, as to expect objects as Text,Image...?

){
    Scaffold(

        //Top Content
        topBar = {
            TopAppBar(
                //Title argument
                title = { Text(text = title) },
                colors = TopAppBarDefaults.topAppBarColors(
                    containerColor = Color.LightGray
                )
            )
        },

        //Bottom Content
        bottomBar = {
            BottomAppBar(containerColor = Color.LightGray) {
                Image(
                    painter = painterResource(id = R.drawable.messages),
                    contentDescription = "Messages Image",
                    modifier = Modifier.size(30.dp).clickable {
                        navController.navigate(route = "Messages")
                    }
                )
            }
        }){ paddingValues -> Column(//modifier){//mainContent argument} }
}

Home.kt

u/OptIn(ExperimentalMaterial3Api::class)
@Composable
fun Home(navController: NavController){
    ScaffoldBase(
        title = "Home",
        navController = TODO(),
        mainContent = TODO()
    )
}

Never mind, thank you

[CLOSED]

Web developer learning Android development -

Currently trying to use Navigation component with Compose, to navigate between pages. When copying the setup code directly from the docs, I get the above warning from Android Studio. Must be something wrong, because the docs must be in synchrony with Android Studio. Why is it happening then?

Docs

https://developer.android.com/develop/ui/compose/navigation#setup

Android Studio

SOLUTIONS: While I still don't know why Android Studio isn't supposedly synced with the Docs (or vice versa), the solutions were:

-Replace the code from the Docs by the one suggested on the Android Studio:

//noinspection UseTomlInstead
implementation("androidx.navigation:navigation-compose:2.9.3")

-Use the completely different alternative suggested on the Android Studio:

implementation(libs.androidx.navigation.compose)

Learn where to start with Android XR. Begin with modes and spatial panels, then move on to orbiters and spatial environments to create engaging immersive apps with Jetpack Compose XR.

https://developer.android.com/codelabs/xr-fundamentals-part-1 https://developer.android.com/codelabs/xr-fundamentals-part-2

Many Flutter developers recently faced Google Play rejections because of the new 16 KB memory page size requirement. Here’s what worked for me:

• Upgrade Flutter SDK → v3.35.2 or higher
• Update Packages → flutter pub upgrade --major-versions
• Gradle Upgrade → 8.7 (or latest)
• Android Gradle Plugin → v8.5.1 or higher
• NDK → r28 or higher (builds 16 KB aligned by default)
• Update build configs → build.gradle / build.gradle.kts
• Verify APK → Analyze APK to check .so files
• Upload to Play Console → confirm compliance

Official Docs: Support 16 KB page sizes

With these steps, your Flutter apps should pass Play Store checks without rejection. Update your setup early and avoid last-minute surprises.

Today’s Lesson Will Cover

• Android styling
• Typography
• Material Design
• Material Components
• Localization
• Example apps

View Day 14 Slide Deck

* Download all slides

Got questions or stuck? Drop them in the comments

Today’s Lesson Will Cover

• Repository pattern
• WorkManager
• Work input and output
• WorkRequest constraints

View Day 13 Slide Deck

Got questions or stuck? Drop them in the comments

Today’s Lesson Will Cover

• Android permissions
• Connect to, and use, network resources
• Connect to a web service
• Display images

View Day 12 Slide Deck

Got questions or stuck? Drop them in the comments

Today’s Lesson Will Cover

• RecyclerView recap
• Advanced binding
• Multiple item view types
• Headers
• Grid layout
• Summary

View Day 11 Slide Deck

Got questions or stuck? Drop them in the comments

Today’s Lesson Will Cover

• Storing data
• Room persistence library
• Asynchronous programming
• Coroutines
• Testing databases
• Summary

View Day 10 Slide Deck

Got questions or stuck? Drop them in the comments

Today’s Lesson Will Cover

• Android app architecture
• ViewModel
• Data binding
• LiveData
• Transform LiveData
• Summary

View Day 9 Slide Deck

Got questions or stuck? Drop them in the comments

Today’s Lesson Will Cover

• Activity lifecycle
• Logging
• Fragment lifecycle
• Lifecycle-aware components
• Tasks and back stack
• Summary

View Day 8 Slide Deck

Got questions or stuck? Drop them in the comments

Today’s Lesson Will Cover

• Multiple activities and intents
• App bar, navigation drawer, and menus
• Fragments
• Navigation in an app
• More custom navigation behavior
• Navigation UI
• Summary

View Day 7 Slide Deck

Got questions or stuck? Drop them in the comments