Software Development · Mobile Apps
Develop an attendance app with QR codes
Teachers show a changing QR code; students scan it to mark attendance, with safeguards against proxies.
- DifficultyAdvanced
- Estimated time1–3 months
- Budget₹0
- ClassCollege, years 2–4
- Team2–4 people
- You needComputer only
Prerequisites: None beyond your class work
Original · by TechnifyedFinal-Year ProjectMobile AppFree to doComputer onlyPortfolio focused
Overview
Teachers show a changing QR code; students scan it to mark attendance, with safeguards against proxies.
Skills you will use
Safety
- This project handles personal data. Collect the minimum, store it safely, get permission, and delete it when the project ends.
Materials and tools
- Computer
- Two Android phones
- A free backend tier
Tools and software
Step-by-step roadmap
Start
You will finish with: a working app with reports and a section on how proxies are prevented and what remains possible.
- 1
Prerequisites
Nothing special to know first. Then collect the 3 items in the materials list.
- 2
Learn
Read up on mobile apps: attendance, authentication, QR code. Your textbook chapter and one short video are enough.
- 3
Plan
List the features for version one, sketch the screens or data flow and pick the tools. Keep the first version small.
- 4
Build
- Build teacher and student logins.
- Generate a QR code that changes every 15 seconds for a class session.
- Let students scan it and record attendance on the server.
- Add checks: one device per student and an optional location match.
- Build reports by student and by subject.
- Test with a real class of ten people.
- 5
Test
Try it with wrong, empty and unusual input, and ask someone else to use it without your help.
- 6
Document
Write a README: what it does, how to run it, screenshots and what you learned. Report structure
- 7
Present
Show a live demo of one complete task, then the design and the hardest problem you solved. Presentation structure
- 8
Publish
Put the code on GitHub with the README and, if you can, deploy a live demo.
Expected outcome
A working app with reports and a section on how proxies are prevented and what remains possible.
Other versions of this project
Advanced version
Add offline mode and export to the college's spreadsheet format.
Ways to do this project
Text marked "You write this" is a prompt for your own work; everything else is specific to this project.
- Research question
- You write thisOne question you can answer with data, narrow enough to finish in the time you have.
- Hypothesis
- You write thisWhat you expect to find, and why.
- Variables
- You write thisWhat you change or compare, what you measure, and what you hold constant.
- Methodology
- You write thisDescribe the method in enough detail that someone else could repeat it: sample, tools, procedure.
- Data collection
- You write thisSay what you will record, how many times, and how you will keep the records safe.
- Analysis
- You write thisChoose the table, chart or test that answers the question; report averages with their spread.
- Limitations
- You write thisList what could have affected the result: small sample, instrument limits, things you could not control.
Literature review
Find five to eight sources (your textbook, review articles, reports) and note what each says about your question. Group them by idea, not one after another, and end with what is still not known.
References
List every source you used in one style throughout (author, year, title, where it was published, link and the date you opened it).
Use this as the outline of your README or case study.
- Problem
- You write thisThe problem in one or two sentences.
- Why it matters
- You write thisWho has this problem and what it costs them.
- What was built
- A working app with reports and a section on how proxies are prevented and what remains possible.
- Technology
- Firebase, Flutter
- Architecture
- You write thisOne diagram: the parts and how data moves between them.
- Implementation
- You write thisThe 6 build steps in your own words, with one code or design decision you are proud of.
- Challenges
- You write thisThe hardest bug or decision, and how you got past it.
- Results
- You write thisNumbers: accuracy, speed, users, survey answers.
- Demo and code
- You write thisA link to a live demo or a short video, and to the GitHub repository.
- Lessons learned
- You write thisWhat you would do differently next time.
- Future improvements
- Add offline mode and export to the college's spreadsheet format.
- Problem
- Teachers show a changing QR code; students scan it to mark attendance, with safeguards against proxies.
- Target user
- You write thisOne specific person: who they are and when they would use this.
- Solution
- Teachers show a changing QR code; students scan it to mark attendance, with safeguards against proxies.
- First version (MVP)
- You write thisThe smallest version that shows the idea working once, end to end.
- Tech stack
- Firebase, Flutter
- Architecture
- You write thisA quick sketch of the parts and how they connect.
- Demo
- You write thisThe one scenario you will show live, start to finish, in under two minutes.
- Stretch goals
- Add offline mode and export to the college's spreadsheet format.
Team roles
Plan by length
24-hour
- Hours 0–2: agree the problem, the user and the one thing the demo must show
- Hours 2–16: build only the first version
- Hours 16–20: test the demo path end to end and fix what breaks
- Hours 20–24: slides, a 2-minute demo script and a backup recording
48-hour
- Evening 1: problem, user, sketch and task split
- Day 1: first version working end to end
- Day 2 morning: one stretch goal and testing
- Day 2 afternoon: polish, slides and demo practice
1-week
- Day 1: research the problem and talk to two possible users
- Days 2–4: first version
- Day 5: stretch goals
- Day 6: testing and write-up
- Day 7: demo video and presentation
Working as a team
2–4 people. Suggested roles:
Report and presentation
Report structure
- Title and summary
- Problem and target user
- Features
- Tools and technology
- Design: architecture, data model or screens
- Implementation
- Testing
- Results and screenshots
- Challenges
- Future improvements
- References
Presentation structure
- The problem
- Who it is for
- Live demo
- How it is built (one diagram)
- The hardest part
- Testing and results
- What you learned
- What comes next
Viva questions
Prepare your own answers to these before you present.
- What is the aim of your project, in one sentence?
- What is the principle behind it?
- Why did you choose these materials or tools?
- What result did you get, and was it what you expected?
- What went wrong and how did you fix it?
- How could this be improved or used in real life?
Resources
Source and attribution
Original
Written by Technifyed. Free to use for your own school or college project; write the report in your own words. Added 1 Oct 2026.
Similar projects
More Software Development projects
Software Development · Mobile Apps
Build an expense tracker mobile app
Create an Android app to record expenses by category and see monthly charts.
Software Development · Mobile Apps
Build a habit tracker with streaks
Create an Android app to tick off daily habits and see streaks and a calendar heat map.
Software Development + Applied Mathematics
Create a school timetable generator
Generate a clash-free timetable from teachers, subjects, rooms and periods.
Software Development + Entrepreneurship
Build a price comparison tool for textbooks
Let students list and find second-hand textbooks on campus and compare prices.
Same tools
Health Technology + Software Development
Design an app that reminds elders to take medicine
Build a simple reminder app with large text and test it with an older relative.
Two-subject alternatives
Public Policy and Governance + Software Development
Build a civic-tech prototype to report local problems
Build a site where residents mark potholes or broken lights on a map and track their status.
Operations, HR and Supply Chain + Software Development
Build a simple online store prototype
Create a small store for hand-made or second-hand items and test it with ten users.
EdTech and Study Tools + Software Development
Build a flashcard app with spaced repetition
Make a web app that shows each card again just before you would forget it.
Graphic and UI/UX Design + Software Development
Redesign an app you use every day
Find real problems in an app through user tests, redesign one flow and prove your version is better.
Same difficulty and budget
Artificial Intelligence · Computer Vision
Recognise Indian sign language letters
Collect images of static signs, train a classifier and test it with people who did not provide training data.
Artificial Intelligence + Agricultural Technology
Recognise plant diseases from leaf photos
Train a model on public leaf images to tell healthy leaves from diseased ones and test it on your own photos.
Data · Data Engineering
Build a data pipeline that runs every day
Fetch a public data feed daily, clean it, store it in a database and chart the history.
Artificial Intelligence · Computer Vision
Build an image search engine
Find visually similar images by comparing feature vectors from a pretrained network.