Android

Looking back at the XML days of Android development feels like looking at black-and-white television. It worked, but boy, was it clunky. Today, in 2026, Jetpack Compose isn’t just “the new way”—it’s the only way that makes sense for modern Android apps. Declarative is King The shift from imperative (“find this view and set its text”) to declarative (“here is the state, describe how it looks”) has probably saved me thousands of hours of debugging weird UI states. No more null view references. No more findViewById. ...

Sometimes we want to show the user an alert when somethings wrong or we just need to give some extra info, For example; Ask the user if he is sure he wanna leave the app. This can be achieved with the following code (runs inside activity): AlertDialog.Builder(this) .setMessage("Are you sure you want to exit?") .setCancelable(false) .setPositiveButton("Yes", object:DialogInterface.OnClickListener() { fun onClick(dialog:DialogInterface, id:Int) { this@YourActivity.finish() } }) .setNegativeButton("No", null) .show() This works fine, buy there is one annoying issue, If user clicks home button while dialog displayed, and go back to the app, the dialog will still be there. Now your user experience is seeing a question about getting out of the app while he just went in. ...

When working with MutableLiveData you can update the observable value in 2 ways: setValue postValue Both will update the live data value as expected as long as your code is running from the main thread. If you need to update a value from other thread you can use the postValue which is thread safe, and will make sure to notify observers on main thread. This is all nice, but be aware! ...

Just noticed this method available from API 11 only,  so you should find another implementation to avoid unexpected behaviour. Or don't call the execute method,  why?  If you'll check documentation you'll see that in some versions of android all tasks will run synchronouslly on the same background thread and on some versions it'll run on a pool of threads. Always use the executeOnExecutor option for consistent behaviour between platform version and avoid unexpected behaviour. ...