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
A cheap data bundle may expire before the end of a trip or cover only part of the itinerary. DataTrip is a graduation project that compares the complete fit of a plan rather than sorting offers by their headline price. It is especially easy to demonstrate with a small, clearly labelled catalogue.
Start with manually entered eSIM, roaming and local data offers. The traveller adds trip dates, destinations and expected usage. The app filters incompatible options and explains the cost of covering the journey. It does not need to sell connectivity or activate a SIM to prove that its comparison is useful.
The first user journey
- The user enters the itinerary, a daily usage estimate and a reserve percentage for unexpected needs.
- They record device compatibility and unlocking information as confirmed or unknown, using their device and provider guidance.
- The app checks each offer’s destinations, data allowance, validity start rule and any stated hotspot restriction.
- The user compares eligible plans, saves the assumptions and follows the provider’s link to verify current terms before purchase.
The logic that makes the project distinct
Estimate data demand from trip length and daily usage, then apply the reserve once. Eligibility comes before ranking: a plan that does not cover one destination should not appear cheapest without a visible gap. Keep activation-on-installation and activation-on-first-use as different rules when the provider specifies them.
Treat unlimited plans carefully. Store the supplied fair-use or speed conditions instead of converting the word unlimited into infinite high-speed data. If topping up is part of the comparison, it must be a documented option. Unknown compatibility should remain a question, not become a successful validation.
estimated data = travel days × daily GB × (1 + reserve fraction) eligible = coverage AND validity AND confirmed compatibility for the chosen offer
A classroom demonstration
For a fictional ten-day trip, 0.6 GB per day with a 25% reserve gives 7.5 GB. A 5 GB offer is insufficient under those assumptions, while a 10 GB offer may fit. However, if the second offer lasts only seven days, it still fails the duration check unless a documented extension covers the rest of the 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 |
|---|---|
| Itineraries | Dates, destinations and daily data assumptions. |
| Offers | Allowance, validity rule, coverage, price, currency and source date. |
| Checks | Compatibility, restrictions, missing information and saved comparison. |
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
A paid feature could compare complex multi-country itineraries and preserve several plan scenarios for a frequent traveller. Begin by charging for the planning report rather than presenting an unimplemented telecom checkout. If affiliate relationships are added later, disclose them and keep the comparison logic understandable.
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 DataTrip as a graduation project in Egypt. Focus on matching travel data offers to dates, destinations and realistic usage. Define the smallest catalogue, the difference between eligibility and price ranking, and a paid comparison report. Propose tests for validity, unknown device compatibility and fair-use information.
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 DataTrip with an English frontend, backend, database, authentication and payments. Add itineraries, daily usage estimates and manually sourced plan offers. Filter by coverage, validity and compatibility before comparing cost. Save each user’s scenarios and add a paid report with verified payment access. Display source dates and unknown conditions; do not claim live prices, activation or guaranteed network performance.
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
- Use the ten-day example and reject a seven-day plan even when its data allowance is sufficient.
- Remove coverage for one itinerary country and display the uncovered segment.
- Change the reserve from 25% to 0% and verify that the requirement changes from 7.5 GB to 6 GB.
Measure how often users notice a coverage or validity mismatch with the app versus a simple price list. A later catalogue integration should preserve the source timestamp and conditions. Network speed predictions are a separate problem and should not be inferred from the size of the data bundle.
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.
Does a low price per gigabyte make a plan best?
Only after its validity, coverage, compatibility and relevant restrictions fit the trip. The app should show those checks before the price ranking.
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.