Skip to content
Home/Resources/Software Development/Mobile app project ideas
Roadmap · Software Development

20 Mobile App Project Ideas for Indian Students: Stack, a Stand-Out Upgrade and What to Show Recruiters

By Younus FardeenUpdated 11 Nov 202610 min read
Short answer

Pick a mobile app project that solves a problem you have, finish three screens and one data store, then add one upgrade that makes it yours. This page gives 20 ideas from beginner to advanced for Indian students, each with a stack, a stand-out upgrade and the evidence to show recruiters, plus open data sources and a tested settle-up function.

These ideas are written for Indian students building a portfolio, a mini project or a final-year project. Each has a stack, a stand-out upgrade and the evidence that lets a reviewer check your work in five minutes. Data sources and platform rules were checked on 11 November 2026.

Pick your stack first with Flutter vs React Native vs Kotlin vs Swift, and follow the mobile development roadmap if you are still learning the basics.

How to choose one and actually finish it

  • Pick by level, not by buzz. Take the first three from your level and choose the one you would use yourself.
  • Define done before you start. Three screens, one data store, a README and a build that runs on a real phone.
  • Add exactly one upgrade. The upgrade is what makes the project yours. Two upgrades usually means an unfinished app.
  • Test the rule that must never break. For an app with accounts, a second user must never see the first user's data. The security checklist has the steps.
  • Use AI tools as a typist. The Expo and AI agent guide shows a full build with a spec, small steps and tests. More ideas that suit this style are in the vibe coding project ideas.

For a web or backend project instead, see the frontend project ideas, or the final-year project ideas if your college needs a report and a viva.

20 project ideas, beginner to advanced

Beginner (1 to 7): one screen of logic, local data

#ProjectStackStand-out upgradeWhat to show recruiters
1Tip and bill splitterAny stack, no backendA rounding rule you can explain, and the last tip percentage rememberedA 30-second screen recording and unit tests for rounding
2Habit tracker with streaksExpo or Compose, local storageA daily reminder and a clear rule for missed daysThe streak rules written as tests
3Offline notesSQLite through your framework (Room on Android)Search across notes and export to a text fileAn airplane-mode demo
4Local-language flashcardsFlutter or Compose with SQLiteSpaced repetition with Leitner boxes, and text that renders correctly in a regional script on a low-end phoneScreenshots in two scripts and where your word list came from
5Expense log with a category chartAny stack with SQLiteA monthly CSV export and a budget warningThe chart screen and the exported file
6Exam quiz app from a JSON fileAny stackA timer, a review of wrong answers and a stored best scoreA README showing how to add 100 questions without touching code
7Weather appAny stack with Open-MeteoCache the last result and show an 'updated at' time when offlineScreenshots of the no-network and error states

Intermediate (8 to 14): accounts, data sources, device features

#ProjectStackStand-out upgradeWhat to show recruiters
8UPI-style expense splitter (screens only, no real money)Flutter, Compose or React Native with SupabaseBuild a upi://pay link from a payee ID and amount, so friends pay in their own UPI app. Your app never handles moneyThe settle-up function with tests, and a two-account privacy test
9Metro timetable from open dataAny stack with the Kochi Metro static GTFS feed'Next train from my stop' that works offline from a bundled copy, with the required attribution lineThe attribution text and your data-update script
10Attendance and 'can I skip' trackerAny stack with SQLiteA target percentage per subject and an alert before you drop below itA real semester of your own use
11Campus event board with push notificationsFirebase Auth and Cloud Messaging, or SupabaseOrganiser and student roles enforced by security rulesTests proving a student cannot edit an event
12Kirana stock scannerML Kit barcode scanning with SQLiteA low-stock list and a shareable reorder messageA demo scanning ten real packets, working offline
13Bill scannerML Kit text recognitionExtract the total and date and send them to project 5 or 8Accuracy on 20 real bills, before and after your fixes
14Mandi price viewerAny stack with data.gov.in commodity price dataA regional-language screen, cached data and a price-drop alertThe dataset link, its update date and its licence

Advanced (15 to 20): sync, on-device AI, shared code, release

#ProjectStackStand-out upgradeWhat to show recruiters
15Offline-first sync appRoom or SQLite with Supabase or FirestoreA written conflict rule (last write wins or merge), tested on two phones in airplane modeA sequence diagram and the test log
16On-device AI note summariserApple Foundation Models on iOS 26 or later, or ML Kit GenAI APIs on AndroidA graceful fallback on phones that do not support itA table showing what runs on the device and what leaves it
17Habit app with Kotlin MultiplatformShared Kotlin module, Compose on Android, SwiftUI on iOS (needs a Mac)Shared tests that run on both platformsA module diagram and how many lines are shared
18Civic issue reporter on a mapMapLibre with Supabase and photo storageAn offline queue for reports made with no signal, and a moderation screenA map screenshot and the access-rule tests
19Live location sharing for friendsFirestore or Supabase RealtimeCorrect background-location permissions and a battery testA permission-flow video and battery numbers
20Ship to Google Play closed testingAny Android app, GitHub Actions and CrashlyticsA signed build on every tag and a crash-free rate on a dashboardThe testing link, a CI badge and release notes

Project 19 teaches a rule that surprises beginners. Android 10 restricted background location access, and Android 11 requires foreground and background location permissions to be requested separately. Project 20 has its own rule: a new personal Play account needs a closed test with at least 12 testers for 14 days before production access.

Open data and APIs for these projects (checked 11 November 2026)

SourceProjectsWhat to know before you build
data.gov.in14India's Open Government Data platform. The mandi price dataset page states its datasets are licensed under the Government Open Data License-India. Check each dataset's update date
Kochi Metro open data9Static GTFS for routes, schedules and fares. Free to use and redistribute with the line 'Contains data provided by Kochi Metro Rail Limited'. KMRL does not guarantee updates
Delhi Open Transit Data9Static GTFS is public and its stop times are approximate. Real-time vehicle positions need an authorised key
Open-Meteo7A free JSON API with no sign-up for non-commercial use. Commercial use needs a plan
MapLibre18Open-source mapping libraries, including native ones for Android and iOS. You also need a map tile source, so read its terms
ML Kit12, 13, 16On-device barcode scanning and text recognition that work offline, plus GenAI APIs on Android powered by Gemini Nano
Foundation Models16Apple's framework, introduced with iOS 26, for the on-device and Private Cloud Compute models behind Apple Intelligence
Google Pay UPI guide8Shows the upi://pay link with the pa, pn, tn, am and cu parameters and points to NPCI's UPI Linking Specification. Read it before building

More datasets for projects are listed on the free datasets page, and backends and sign-in options on the free backend tools page.

Settle-up logic you can run and test first

Project 8 depends on one function: given who paid and who shared, who pays whom. Write and test it before drawing any screen. This JavaScript version works on its own in Node, and the same logic ports to Kotlin, Swift or Dart. It stores money in whole paise so rounding never drifts, and gives leftover paise to the first people in each share.

// Amounts are whole paise (Rs 1 = 100 paise), so rounding never drifts.
function settle(expenses) {
  const net = {};
  for (const { paidBy, paise, sharedBy } of expenses) {
    const base = Math.floor(paise / sharedBy.length);
    let extra = paise - base * sharedBy.length; // leftover paise go to the first people
    net[paidBy] = (net[paidBy] ?? 0) + paise;
    for (const person of sharedBy) {
      net[person] = (net[person] ?? 0) - (base + (extra-- > 0 ? 1 : 0));
    }
  }
  const owes = [], gets = [];
  for (const [name, bal] of Object.entries(net)) {
    if (bal < 0) owes.push([name, -bal]);
    if (bal > 0) gets.push([name, bal]);
  }
  const payments = [];
  while (owes.length && gets.length) {
    const pay = Math.min(owes[0][1], gets[0][1]);
    payments.push(`${owes[0][0]} pays ${gets[0][0]} Rs ${(pay / 100).toFixed(2)}`);
    owes[0][1] -= pay;
    gets[0][1] -= pay;
    if (owes[0][1] === 0) owes.shift();
    if (gets[0][1] === 0) gets.shift();
  }
  return payments;
}

const trip = [
  { paidBy: "Asha", paise: 90000, sharedBy: ["Asha", "Ravi", "Meena"] },
  { paidBy: "Ravi", paise: 30000, sharedBy: ["Asha", "Ravi", "Meena"] },
  { paidBy: "Meena", paise: 10000, sharedBy: ["Asha", "Meena"] },
];
console.log(settle(trip));

It prints Ravi pays Asha Rs 100.00 and Meena pays Asha Rs 350.00. Check it by hand: Asha is owed Rs 450 net, Ravi owes Rs 100 and Meena owes Rs 350, and the three balances add up to zero. Add tests for an odd split such as Rs 100 between three people, an empty list and one person paying for themselves. A test that fails on purpose proves the test works.

What to show recruiters

We found no survey of what mobile recruiters weigh, so treat this as a checklist of evidence rather than a rule. The goal is that someone can judge your work without installing anything.

  • A public repository with a README that has the problem, a screenshot, the stack, how to run it and one known limit. See the GitHub profile guide.
  • A 60-second screen recording of the main flow on a real phone.
  • An install path: a shared APK, a Play testing link or a TestFlight link. Google's limited distribution accounts let students share an Android app with up to 20 devices without a government ID or fee.
  • Tests for the one rule that matters, such as the settle-up maths or the privacy rule.
  • A short note on what you would do next, which shows you know the limits of the version you shipped.

Looking for more ideas outside mobile? The software development projects and free projects with source code pages cover web, backend and tools.

Frequently asked questions

What is a good mobile app project for a beginner?

A habit tracker or an offline notes app. Both need three screens and local storage, and both fit the first weeks of any roadmap. Add one upgrade, such as a reminder or search, and write tests for the rule that matters, so the project shows judgement and not only a tutorial.

Which mobile app project is best for a final-year project?

Choose one with real users, a data problem and some depth, such as an offline-first sync app, a campus event board with roles or a civic issue reporter. Colleges ask for a report and a viva, so keep a design document and a test log. The final-year project ideas page covers the paperwork.

Can I build these mobile app projects with AI tools?

Yes. Write a spec, ask for one screen at a time, read every change and test on a real phone. You must be able to explain the code in an interview. The Expo and AI agent guide shows a full build, and projects with accounts need a two-account privacy test.

How do I show a mobile app in a portfolio without publishing it?

Share the repository, a 60-second screen recording and an install path. On Android, a shared APK works, and Google's limited distribution account allows up to 20 devices with no government ID or fee. On iPhone, TestFlight needs the paid Apple Developer Program, so a recording may be enough.

Which stack should I use for mobile app projects?

Use the stack you are learning. Kotlin with Jetpack Compose suits Android, Swift with SwiftUI suits iPhone, and Flutter or React Native suit both. The comparison page gives a decision table and India hiring signals, but finishing one app matters more than the stack.

Do I need to publish my app on the Play Store?

No. Many good portfolio apps never reach a store. A new personal Play account must run a closed test with at least 12 testers for 14 days before production access, so plan weeks for it. Publish only if you want the experience of review, signing and release notes.

Sources checked

Learn this with mentors

Programmes for builders and engineers with admissions open: live classes, mentors and project work.

Continue learning

Roadmap

Mobile app development roadmap

Pick a platform, follow the free roadmap, know store fees, ship in 12 weeks

Open →
Roadmap

Flutter vs React Native vs Kotlin vs Swift

A decision table, India hiring signals and the best first stack

Open →
Project guide · Vibe coding

Vibe coding projects

36 apps to build with AI, each with a stand-out upgrade.

Open guide →36 ideas