The key idea
Good graduation project ideas share four things: a real user, a real problem, a result you can measure, and a scope a small team can finish in one academic year. Pick the idea you can show working live to the committee, and decide in the first week what you will measure.
What makes a graduation project idea good?
A graduation project idea is good when you can answer four questions before you write code: who will use it, what problem it solves for that person, which number will prove it, and whether a small team can finish it in the academic year. Compare a weak answer with a strong one:
| Question | Weak answer | Strong answer |
|---|---|---|
| Who is the user? | Everyone | First year students who are learning to program |
| What is the problem? | People need an AI tool | They lose hours because they cannot read error messages |
| What will you measure? | Users will like it | Test scores before and after two weeks of use |
| Can the team finish it? | Ten features, each half done | One main function that works from start to end |
What you can build without your own backend
The backend is the part of a website that visitors do not see: accounts, saved data, payments. For many ideas you can add ready backend services from Gammal Tech with one script, and spend your year on the frontend and on measuring results. There are five building blocks:
- Sign in:
GammalTech.login()opens a sign in popup. Your website stores no passwords and never receives the user's email, phone number or identity. - User data: one JSON object for each signed in user, which follows the user across visits and devices.
- AI assistant:
GammalTech.ai.ask()returns an answer, and one text, thesystem_prompt, sets the assistant's role, knowledge and limits. It only answers; your code acts. - Payment link: a normal link takes the payment and returns the customer to your page with a token, which your page verifies before it delivers anything.
- Owner email:
GammalTech.notify()sends an email to the project owner only, which suits request forms.
The honest limits
Saved data is per user only. Think of a private locker for each student: nobody can open another student's locker. A notice board that everyone reads is a different thing, so any idea with data shared between users needs your team's own backend: chat between users, public lists, marketplaces, leaderboards, comments.
The services are for websites, not for native mobile apps. Sign in needs a Gammal Tech account, so the students who test your project need their own accounts. Each project has a monthly allowance at no charge of AI calls for signed in users and of login codes; guest AI calls and owner emails are paid. The current numbers are in the Gammal Tech guide.
Ten graduation project ideas you can build as a website
Each idea below needs only the five building blocks plus your own HTML, CSS and JavaScript.
| Idea | What it does for the user | Platform features | What to measure |
|---|---|---|---|
| Course tutor for one subject | Explains one course, asks practice questions and remembers where the student stopped | Sign in, user data, AI assistant | Quiz scores before and after use |
| Flashcards from lecture notes | Turns pasted notes into question cards and shows weak cards first | Sign in, user data, AI assistant | Cards a teaching assistant marks as correct |
| Code explainer for first year students | Explains a program and its error message in simple Arabic, without solving the assignment | Sign in, AI assistant | Test scores with and without the tool |
| Interview practice coach | Asks junior developer interview questions, comments on each answer and saves weak topics | Sign in, user data, AI assistant | A senior developer's rating of first and last answers |
| Arabic support assistant for a local shop | Answers visitors in Arabic about opening hours, delivery areas and returns | Sign in, AI assistant | Correct answers on real customer questions |
| Lesson request page for a training centre | A parent sends a name, a phone number and a preferred time; the centre calls back | Owner email | Time to send a request; count of complete requests |
| Personal expense tracker | Records daily spending and writes a plain monthly summary | Sign in, user data, AI assistant | Time to add one expense; accuracy of categories |
| CV builder with AI review | Suggests clearer wording for a graduate's CV and opens the export after payment | Sign in, user data, AI assistant, payment link | A recruiter's rating before and after the review |
| Paid revision pack page | Opens a revision file you wrote yourself, only after the payment is verified | Payment link, sign in, user data | Test cases: real payment, cancelled payment, repeated check, faked success link |
| Plain Arabic rewriter | Rewrites a difficult notice in simpler Arabic for people who find reading hard | Sign in, AI assistant | Understanding scores on both versions of a text |
The AI assistant does not read your site by itself, so the shop's details or the course notes go inside the system_prompt, or the user pastes them. Payments have no test mode: every payment is real money, so test with the smallest amount. If you sell to the public, taxes and licences stay your responsibility, so ask a qualified accountant.
How to choose between two or three ideas
Ask four questions about each idea on your short list.
- Team skills. If two of you write good frontend code and nobody has built a server, choose an idea that needs only per user data.
- Your supervisor's field. A supervisor who works on online learning can guide a course tutor better than an expense tracker.
- Data you can really get. A shop assistant needs real customer questions, for example from a bookshop owner in Mansoura. A course tutor needs the lecturer's permission to use the notes.
- A live demo. Choose the idea you can show working in a few minutes with a real account.
A short code sample: sign in, save, read, ask
This page is the skeleton of the interview practice coach:
<script src="https://api.gammal.tech/sdk-web.js"></script>
<button id="start">Start practice</button>
<p id="answer"></p>
<script>
const role = 'You are an interview coach for junior developers in Egypt. ' +
'Ask one question at a time, then give short feedback on the answer.';
document.getElementById('start').onclick = async () => {
await GammalTech.login();
await GammalTech.user.save({ weakTopic: 'SQL joins' });
const data = await GammalTech.user.get();
const reply = await GammalTech.ai.ask(
'Ask me one interview question about ' + data.weakTopic,
{ system_prompt: role }
);
document.getElementById('answer').textContent = reply;
};
</script>The click handler calls GammalTech.login() because browsers may block a popup that does not follow a user action. user.save writes the weak topic into this user's own JSON object, and user.get reads it back on this visit or on another device. The system_prompt keeps the assistant in the role of a coach.
There is no API key to hide in this code, because requests work only from a domain you registered in your project.
What the discussion committee usually asks
Committees in faculties of computers and information in Egypt often return to the same five questions. Prepare one proof for each.
- Problem statement: who has this problem, and how do you know? Bring notes from short interviews with real users.
- Comparison with existing solutions: what is different in yours? Bring a small table that compares two or three of them with your project.
- Testing and results: how do you know it works? Bring written test cases, the numbers before and after, and how many people took part.
- Privacy and security: what data do you collect, and why? Here you can say that the website stores no passwords.
- Limits and future work: what does it not do? If your page unlocks paid content with frontend code alone, admit that a curious user can read anything sent to the browser, and name a server side check as future work.
A simple timeline for the academic year
Divide the year into five periods, each ending with something to show your supervisor.
| When | What the team finishes |
|---|---|
| First month | Choose the idea, interview five possible users, write the problem and the measurement plan, apply for the account |
| Months two and three | Build a plain first version that works from start to end |
| Around the first term exams | Test with real users and collect the first numbers |
| Second term | Fix what the test showed, measure again, write the comparison |
| Last six weeks | Stop adding features, write the documentation, rehearse the live demo |
Apply early: each person has one Gammal Tech account, and approval can take up to 10 days. Agree in the first week who creates the project, and ask your test users to apply too.
Questions students ask about graduation project ideas
Can we use AI in a graduation project in Egypt?
Ask your supervisor first, because each faculty sets its own rules. In every case, document what the AI assistant does inside the project and what your team designed, wrote and tested.
Do we need our own backend?
Not for the ideas in the table, because each needs only data that belongs to one user. Shared data, such as a chat, a public list or a leaderboard, needs your own backend.
Can we build a mobile app with these services?
They are made for websites, not for native mobile apps. A website that works well in a phone browser is the practical choice; ask your supervisor whether your faculty accepts it.
How much does Gammal Tech cost for a student project?
Each project has a monthly allowance at no charge of AI calls for signed in users and of login codes. Guest AI calls, owner emails and payments have costs. The current numbers are in the Gammal Tech guide.
Source and service details
Integration and pricing details are based on the Gammal Tech guide. Check the documentation before publishing or changing your project configuration.