11:18:24 AM NPT Arduino, Robotics & IoT tutorials for Nepal
Beginner

12 Web and Mobile App Project Ideas for BSc CSIT (with Algorithm to Show in Viva)

12 web and mobile app project ideas for BSc CSIT with tech stack, difficulty, an algorithm to explain in viva, and a twist to stand out.

On this page
12 Web and Mobile App Project Ideas for BSc CSIT (with Algorithm to Show in Viva)

A common complaint about web and mobile app projects is that they are "just CRUD": forms that create, read, update and delete rows in a database. A system like that can work perfectly and still be hard to defend, because there is nothing to explain except the screens.

The fix is simple. Pick an idea where you can name one real algorithm or technique and show it on paper with a small example. This list gives you 12 ideas, each with a stack, a difficulty level, the algorithm to point to and a twist. It is general advice from students and supervisors, not an official rule, so check your department's format and your supervisor's expectations.

The 12 ideas

Scroll sideways to see all columns.

# Idea Suggested stack Level Algorithm to show in viva Make it stand out
1 Bus and microbus route finder React or Flutter, Node.js, MongoDB or PostgreSQL Medium Dijkstra shortest path, with stops as nodes with nonnegative fare or time as edge weight Let users choose "fewest transfers" or "cheapest" and compare both results
2 Online exam system MERN, or Laravel and MySQL Medium Seeded shuffling of questions (Fisher-Yates) and a timer enforced on the server Log tab switches and show a per-student timeline for the teacher
3 Timetable generator for a college Django or Laravel, PostgreSQL Hard Backtracking or graph colouring for conflict-free slots Show a manual timetable versus generated one, with the number of clashes removed
4 Expense splitter for friends and hostels Flutter, Firebase or Node API Easy Greedy settlement to reduce the number of payments Show "6 payments reduced to 3" with an example
5 Blood donor finder Flutter or React, Firebase, Google Maps API Medium Haversine distance formula to rank nearby donors Add a "last donated" filter so donors are not contacted too soon
6 Hospital or clinic token and queue system Laravel, MySQL, SMS or push notifications Easy Priority queue (emergency first, then arrival time) Estimate waiting time from the average consultation time
7 Job and internship portal with matching Django or Spring Boot, PostgreSQL Medium Jaccard similarity between candidate skills and job skills Explain the score for each match so users trust it
8 E-library with search suggestions Node.js and React, or Flutter, PostgreSQL Medium Levenshtein edit distance for "did you mean", and an inverted index for fast search Compare search time with and without the index on a few thousand records
9 QR-based class attendance Flutter, Node.js or Laravel Medium Time-limited QR token signed with HMAC so screenshots expire Reject duplicate submissions per authenticated student and explain that a shared code can still work before expiry
10 Local farmer marketplace React or Flutter, Node.js, MongoDB Medium Weighted ranking of listings by price, distance and freshness Let farmers see a simple price trend from a moving average
11 Offline-first note and task app Flutter with SQLite, sync to a server Medium Last-write-wins sync with timestamps, and a discussion of conflicts Show two devices editing the same note and how your rule resolves it
12 Student feedback and complaint tracker Laravel or Django, MySQL Easy Keyword-based category detection with TF-IDF, then ticket routing Show which keywords triggered a category and let admins correct it

Short notes on the algorithms

You do not need to implement anything fancy. You need to explain it clearly.

  • Dijkstra (idea 1): start at the source with distance 0, repeatedly pick the unvisited node with the smallest distance, and update the distances of its neighbours. Draw a graph of five stops and walk through it.
  • Fisher-Yates shuffle (idea 2): go from the last item to the first, swap each item with a uniformly random item from the first through the current position, inclusive. Save the server-generated seed with the exam attempt so you can reproduce the order later.
  • Backtracking (idea 3): assign a subject to a slot, check the constraints (teacher free, room free, section free), and if the next step fails, undo and try another slot.
  • Greedy cash flow (idea 4): compute the net balance of each person, then repeatedly match the largest debtor with the largest creditor. This heuristic reduces transfers but does not guarantee the minimum.
  • Haversine (idea 5): gives the great-circle distance between two latitude and longitude points. It estimates straight-line distance over the Earth’s surface. Use routing data for road distance.
  • Priority queue (idea 6): a heap where the highest priority leaves first. Explain how ties are broken, for example by arrival time.
  • Jaccard similarity (idea 7): size of the shared skills divided by the size of all skills combined, for example 3 shared out of 8 total is 0.375.
  • Levenshtein distance (idea 8): the minimum number of insertions, deletions and substitutions to turn one word into another.
  • HMAC token (idea 9): the server signs a payload (class ID and expiry time) with a secret key. Anyone can read it, but the server rejects changes that fail signature verification. Check expiry and the authenticated student as well.
  • Last-write-wins (idea 11): the record with the latest update time wins, which is simple but can lose edits, so you can discuss better alternatives.
  • TF-IDF (idea 12): gives high weight to words that are frequent in a complaint but rare across all complaints.

Picking the right idea

Scroll sideways to see all columns.

If you... Choose
Have 6 to 8 weeks and a small team 4, 6 or 12
Know Flutter or React Native 4, 5, 9 or 11
Know Laravel, Django or Spring 2, 3, 6, 7 or 12
Want a map in your app 1 or 5
Like security topics 9 or 2
Want a strong viva talking point 3, 8 or 11

What every project in this list should also have

  • Authentication and roles with hashed passwords (bcrypt or similar), never plain text.
  • Input validation on the server, not only in the form.
  • Prepared statements or parameterised ORM queries to prevent SQL injection.
  • A clear database diagram with primary keys, foreign keys and a few sample rows.
  • A test plan with at least ten test cases and the results.
  • A short list of limits: what the app does not do.

Viva tips

  1. Open with one sentence: "Our app helps X do Y, and the key algorithm is Z."
  2. Bring a tiny worked example on paper for your algorithm. Five nodes, four words, or three transactions are enough.
  3. Explain one alternative and why you did not choose it, for example BFS versus Dijkstra.
  4. Know your database: be ready to draw the ER diagram without looking at the screen.
  5. Know what happens on failure: what if the network is off, the input is empty, or two users act at once.
  6. Measure something: response time, number of clashes removed, or payments reduced.
  7. Be honest about what you used from libraries and what you wrote yourself.
  8. Prepare a short demo script of three to four minutes, with sample data already loaded.
  9. Do not guess about rules. If asked about format or marks, say you followed your department's guidelines and show the document.

Common mistakes

  • Choosing five features and finishing none of them.
  • Using a framework generator and not understanding the generated code.
  • Storing passwords in plain text or putting API keys in the repository.
  • Skipping the report until the last week.
  • Showing a demo that depends on fast internet with no backup.

FAQ

Is a CRUD project acceptable?

It may be accepted in some places, but it is harder to defend. Adding one clear algorithm and a measurement usually makes the project far easier to explain.

Should I choose web or mobile?

Pick the one your team can finish. A responsive web app is faster to build and demo. A mobile app feels more real but needs a device, builds and more testing.

Can I combine an app with hardware?

Yes, for example, a mobile app that reads data from an ESP32. Keep the hardware simple and plan the parts early. Our RFID attendance guide shows one way to connect hardware to a web dashboard.

How do I show the algorithm in the app itself?

Add a small "how it works" screen or a debug view that shows intermediate steps, such as the shortest path with distances, or the similarity score for each job. Examiners remember what they can see.

Can two teams choose the same idea?

They can, because the idea is not owned by anyone. What makes your project different is your data, your twist and how well you can explain it.

Related tutorials

See all BSc CSIT Projects →