In A Journey of Migrating to Android Jetpack Compose Part I, I wrote down the steps of how I setup an existing Android project with Jetpack Compose UI framework.
Now I am going to put down the key things that I learnt when rewriting the Settings Screen.
Content in this article:
Since the whole app is still structured by using Bottom Navigation with several Fragments. I want to keep this architecture until we migrate all the screens to Jetpack Compose successfully.
So the first thing…
I am writing down my journey of migrating an existing app (built with traditional Android View system) to an Android Jetpack Compose app. And my plan is to replace the existing screens one by one, and at the same time observe app crash rate and app performance…until a point I want to stop or make it a fully Jetpack Compose Android App.
Be honest to myself is the key of writing this article. (I don’t want to present to like it, just because everyone is talking about Jetpack Compose.)
I will write down the confusion if I feel so, and…
Android 11 changes how apps can query and interact with other apps that the user has installed on a device.
I built several apps, and they share data between each other by using Content Provider in each app.
Recently, one of my apps moved to targetSdkVersion 30, and I found that package visibility change in Android 11 makes apps are invisible to each other in some situation.
This experiment is to find out the simplest solution making my apps visible to each other, regardless the installation order, apps development targetSdkVersion, running Android OS version, or app signatures.
This article is about using Google Map for developing Android native application. Does not cover API pricing, or marketing.
This article does not cover how to set up Google Map project for Android from the scratch either. If you need it, please refer here.
I was building an Android native application by using Google Map SDK. During the development time, I was confused by so many different code examples and API documentation. Now I am trying to write them all down for memorizing and also for sharing some thoughts.
If you are thinking between MapFragment and SupportMapFragment, choose SupportMapFragment.
快赠我幽默感。Sharing is caring.