Android

While building the onboarding screen for my app, I needed a simple text that read something like this: The green hyperlinks are clickable Pretty straightforward, right? Just a bit of text with two clickable links — Privacy Policy and Terms of Service. But as I started implementing it, I realized: there isn’t a single complete guide explaining how to make part of a text clickable using AnnotatedString in Jetpack Compose — especially with the new LinkAnnotation API and a custom URL handler for better control. ...

In the previous article, we explored the power and flexibility of DAOs with Room’s built-in query annotations. But what if your query needs don’t fit into Room’s constraints? Enter @RawQuery – the most flexible and dangerous tool in the Room arsenal. Let’s dive into what @RawQuery is, when it shines and shuns. What is @RawQuery? @RawQuery allows you to execute SQL statements that aren’t validated at compile time. Unlike @Query, which Room parses and validates during compilation, raw queries are evaluated at runtime. ...

In our previous article, we covered Entities in Room. Now, let’s explore DAOs (Data Access Objects) – the bridge between your app and the database. DAOs allow you to execute queries that allow is to insert, update, and delete records efficiently and thats exactly what we are going to explore today. What is a DAO? A DAO is an interface annotated with @Dao that defines methods for interacting with the database. The Room compiler generates the necessary implementation for these interfaces and its methods, which enables us to access the database efficient and type safe. ...

In our previous article, we explored the key components of Room. Now, let’s take a deep dive into Room Entities, their importance, and the various ways to customize them. Entities are the foundation of Room—they define how your data is stored in the database. Properly structuring your entity ensures efficient querying, maintainability, and scalability. Let’s break it down! 🛠️ 🏗️ What is an Entity? An Entity in Room represents a table in the database. Each instance of the entity corresponds to a row in the table, Room generates corresponding SQL table schema based on how you create an entity class. ...

👋 Intro On the previous article we have set-up the Room dependencies and plugins, Now lets get into the primary key components of a room library. There are three important components: Entity, DAO’s, and Database. Entity represents a single row of a table. (Table structure) DAO’s (Data Access Objects) are interfaces to write queries and define operations. Database is where you associate entities and include the DAO’s you’d like to access from outside. Let’s check it out one by one! 🔍 ...

Before we proceed with the setup, let’s quickly recap why we chose Room: ✅ Compile-time SQL Validation – Catches errors early by verifying SQL queries at compile time. ✅ Kotlin-first Approach – Supports coroutines, Flow, and LiveData natively. ✅ Less Boilerplate Code – Simplifies database interactions while maintaining SQLite’s power. ✅ Seamless Migration Handling – Built-in support for database migrations. For a more detailed explanation, refer to the official Android documentation. ...

Why Should You Care? Making your app offline-first is essential if you want to provide the best user experience. It makes your app significantly faster by reducing the number of network calls, which in turn also reduces server costs. What does Offline-First mean? The core idea is to persist/store remote-fetched data on the device. This allows users to access the data instantly, skipping unnecessary network requests—until the data expires or is invalidated. ...