Your starting point
Use Gammal Tech AI to move from a focused idea to a first working version in minutes when the brief is approved and the required setup is ready. Refine it with [mode: idea], then use [mode: build] for the frontend, backend, database, authentication and payments. Actual build time depends on scope, account readiness and integrations.
The app and the problem it solves
An Egyptian student planning a European rail trip may see a pass advertised at one price while individual tickets have their own restrictions and reservation costs. RailChoice turns the itinerary into a comparison with visible assumptions. The answer depends on the actual legs and dates, not on a blanket claim that a pass always saves money.
The project has a distinct optimisation problem: choose how to cover a fixed itinerary with a limited number of pass travel days and individual tickets. Start with a reviewed synthetic dataset. The goal is to explain the cheapest valid combination under the entered rules, rather than scrape every rail operator.
The first user journey
- The traveller adds each rail leg, its date, an individual ticket quote and whether the chosen pass covers it.
- They enter pass price, validity and travel-day rules from the provider, plus reservation or supplement costs for relevant legs.
- The app compares all-ticket travel with valid pass combinations and shows which days consume the pass allowance.
- The user saves the result and rechecks fare conditions, reservation availability and provider rules before purchasing.
The logic that makes the project distinct
Group legs by the provider’s applicable travel-day definition, not by an assumption that every leg consumes a day. Then compare the savings from assigning each eligible day to the pass. Include required reservations and uncovered legs. Keep unusual overnight rules as explicit reviewed inputs rather than inventing a universal rule.
For a small number of travel dates, enumerate valid combinations and calculate their costs. This makes the result easy to explain. Pass eligibility and reservation availability are separate checks. A low calculated total should remain provisional if a required booking has not been confirmed.
pass strategy = pass price + required reservations + uncovered individual tickets calculated saving = all-ticket total − valid pass-strategy total
A classroom demonstration
In a fictional itinerary, separate tickets total 220 units. A pass costs 170 and required reservations total 35, making a valid covered strategy cost 205 and save 15. If an uncovered leg costs another 30, the strategy becomes 235. The apparent saving disappears. Every figure is illustrative and should be replaced with dated provider quotes for a real trip.
Data, interface and backend
Ask for a full-stack application: a phone-friendly frontend, backend logic, a database for persistent work, authentication for the personal workspace and payments for the defined offer. Start with private user workspaces and a small, inspectable dataset. These records give the model a concrete starting point:
| Record | What it stores |
|---|---|
| Legs | Date, route, ticket quote, currency and fare conditions. |
| Pass rules | Price, validity, travel-day allowance and coverage source. |
| Strategies | Assigned travel days, reservations, uncovered legs and totals. |
With Gammal Tech services, personal app data belongs to the user’s workspace. Signing in does not disclose their Gammal Tech account email, phone number or identity to your app. If a later version shares records between people, specify the sharing model and permissions explicitly in the build brief.
A specific paid offer
Sell a saved multi-itinerary comparison and a printable explanation of the chosen combination. The user buys planning and clarity. The first release can link to providers for actual tickets and passes, keeping the payment for the app distinct from transport purchases and any operator reservation.
Define the deliverable, price and currency before checkout. Confirm payment with the provider and associate the entitlement with the correct order; a success screen alone is insufficient. Complete the required account and payment setup before real use, and review the applicable operating costs and payment terms.
Refine the idea with [mode: idea]
1. Open the conversation. Open the Gammal Tech WhatsApp conversation with +201033998844. Open the link first, then continue inside WhatsApp.
2. Start Idea mode. Copy the following command into a message by itself and press Send. The square brackets [ ] are required; keep the colon and space too.
[mode: idea]3. Wait for the mode-change confirmation, then send the brief. Send the following text as a new message, adapting it to your team. Answer the assistant’s questions about the audience, first version and paid value until the idea is approved.
Refine RailChoice as a computer science graduation project in Egypt. Focus on choosing pass travel days for a fixed itinerary, with individual tickets and reservation costs. Define the smallest solvable dataset, an explainable optimisation method and a paid comparison report. Include cases where a pass appears cheaper until uncovered legs are added.
Build the project with [mode: build]
4. Move to Build after the idea is approved. In the same WhatsApp conversation, send the following command by itself, including the square brackets, then press Send.
[mode: build]5. Wait for the mode-change confirmation, then send the requirements. Use the following message as a starting brief. Agree the scope of the frontend, backend, persistent data, login and payments. Ask about access, setup and fees, and approve the scope and cost before work begins. Simple versions can be prepared in minutes once prerequisites are ready; timing depends on the project scope.
Build RailChoice with an English frontend, backend, database, authentication and payments. Add itinerary legs, dated ticket quotes and reviewed pass rules. Enumerate valid travel-day assignments for small itineraries and show the cheapest recorded strategy with a cost breakdown. Save scenarios per user and add a paid comparison report. Keep eligibility, availability and missing rule information visible.
The buttons prepare the command in WhatsApp. Press Send to start the conversation.
6. Review the result and leave the mode when you finish. Open the project link and try the user journey and test cases described in this article. For a correction, name the page and the result you expect. To return to the normal assistant, send the following command by itself, including both square brackets:
[exit]What to demonstrate at graduation
- Reproduce the 205-unit strategy and then add the uncovered 30-unit leg, producing 235.
- Put two eligible legs on the same provider-defined travel day and verify the correct allowance usage.
- Exceed the pass validity or day allowance and reject that strategy rather than reporting an invalid saving.
Use exhaustive enumeration as a reference on small cases, then compare a faster approach on larger itineraries if needed. Report both correctness and explanation quality. The most useful screen shows why a particular day uses the pass while another uses an individual ticket.
Demonstrate the interface, the decision logic and saved work after login. Explain your own understanding, assumptions and evaluation, following your university’s rules on AI assistance. A classroom demonstration can use clearly labelled sample payment states without making a charge. Those samples are not a Gammal Tech gateway test mode; gateway transactions involve real money.
Should the app assume reservations are included?
No. Record what the specific provider and service require. An unknown supplement or reservation condition should stay visible in the comparison.
Sources and next steps
Recheck sources and service terms when implementing. Fictional data and prices in this article illustrate the project, rather than current offers.