Before building, it helps to understand the world your app will live in: operating systems, app types, and the stores that distribute apps.
Two platforms
- Android, developed by Google, runs on phones from many manufacturers and powers the large majority of smartphones in India. Apps are distributed mainly through the Google Play Store.
- iOS, developed by Apple, runs only on iPhones (and iPadOS on iPads). Apps are distributed through Apple’s App Store.
Each platform has its own design conventions, developer tools, languages and rules.
Types of apps
| Type | How it is built | Strengths | Limitations |
|---|---|---|---|
| Native | Platform languages: Kotlin (Android), Swift (iOS) | Best performance and full access to device features | Two separate codebases for two platforms |
| Cross-platform | One codebase for both, e.g. Flutter (Dart) or React Native (JavaScript) | Faster development, shared code, near-native performance | Occasional platform-specific work |
| Progressive web app (PWA) | A website that can be installed and work offline | No store needed, one codebase with the web | Limited access to some device features, especially on iOS |
| No-code / low-code | Visual builders | Very fast for simple apps | Less flexibility; dependency on the platform |
What happens inside an app
A typical app has:
- a user interface (UI): screens, buttons, lists and forms;
- logic: what happens when users tap, type or swipe;
- data: stored on the device (settings, offline content) and/or on a server reached through the internet (accounts, orders, messages);
- access to device features: camera, location, notifications, contacts, through permissions that the user must grant.
Many apps are the front end of a larger system: the app talks to a back end (a server with a database) through an API (application programming interface), usually over HTTPS, exchanging data in JSON.
The app lifecycle
On a phone, apps are frequently paused, sent to the background, or closed by the system to save memory and battery. Well-built apps save state so users do not lose their work, and they use battery and data responsibly.
Designing for Indian users
- A wide range of devices, including low-cost phones with limited memory and storage: keep the app small and efficient.
- Patchy connectivity: handle slow and offline conditions gracefully.
- Many languages: consider supporting Indian languages, and design layouts that accommodate longer text.
- Data costs and storage space: avoid unnecessary downloads.
- Trust and safety: clear permissions, and no unnecessary access to personal data.
Thinking through an app
A local tuition centre wants an app for homework and fee reminders. It needs: a list of homework by class (data from a server), push notifications (device feature with permission), a fee status screen (server data, secured by login), and offline access to the last homework list (local storage). Even this simple idea involves UI, logic, server data, local data and device features: the building blocks of almost every app.
Try this
Pick two apps you use every day. For each, list: the platform(s), what data it probably stores on your phone versus on a server, which device features it uses, and which permissions it asked for.
Key points
- Android (Google Play) dominates in India; iOS (App Store) runs on iPhones.
- Native, cross-platform (Flutter, React Native), PWA and no-code are the main approaches.
- Apps combine UI, logic, local data, server data through APIs, and device features with permissions.
- Design for low-cost phones, patchy networks, many languages and user trust.