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
Many travel apps list places. StorySteps gives visitors a reason to look closely at them. A traveller follows an original mystery through a small set of public locations, notices details and unlocks the next chapter. Egyptian students can prototype a fictional city first, then adapt the format to a carefully researched real route.
The project is a narrative travel product rather than a generic quiz. Challenges belong to a place and advance a story. The software problem includes branching progress, hints, route order and saved sessions. The creative problem is making the walk interesting without relying on copied guidebook text or misleading historical claims.
The first user journey
- The traveller previews the route length, expected effort, access conditions and story theme before choosing a quest.
- They open the first chapter, inspect a location and answer a short observation challenge, with an optional hint.
- The app saves progress and offers a skip or alternative when a stop is closed or unsuitable for the traveller.
- The final chapter connects the clues and gives the traveller a personal journey summary, without requiring a public leaderboard.
The logic that makes the project distinct
Represent the quest as a directed story graph. Each node contains a location, a scene, a challenge and the permitted next nodes. Store progress separately from the story definition so updating a typo does not erase a traveller’s completed steps. Keep fictional story elements clearly distinguishable from sourced historical facts.
Build recovery into the route. A locked gate or inaccessible stop should not trap the user in the story. Avoid challenges that require entering restricted areas, photographing strangers or handling artefacts. For the first release, a personal progress record is enough; shared multiplayer scoring introduces a different permissions and coordination problem.
quest progress = completed story nodes + current branch + available next steps A skipped physical stop may lead to an accessible story alternative.
A classroom demonstration
Create a five-stop fictional route about a missing map. At stop two, the player identifies a symbol described in your own scene artwork or text. If the location is unavailable, an alternate clue preserves the story and records that the physical stop was skipped. At the ending, the app explains how the clues connect instead of simply awarding points.
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 |
|---|---|
| Quest content | Original scenes, stops, clues, alternatives and source notes. |
| Progress | Current node, completed steps, hints used and branch choice. |
| Access | Purchased quest identifier and verified access status. |
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 individual original quests or themed route bundles. Let visitors preview the opening and understand the walking requirements before checkout. If a route uses a venue or commissioned content, secure the appropriate permission. The paid product is the authored experience, not admission to attractions unless a real arrangement includes it.
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 StorySteps as a creative travel graduation project for students in Egypt. Define a five-stop original narrative quest with observation challenges and an alternate path for a closed stop. Propose a paid route offer and a way to evaluate whether players notice and remember places. Separate fictional storytelling from historical information requiring sources.
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 StorySteps with an English frontend, backend, database, authentication and payments. Create a five-stop fictional demonstration quest, branching scenes, hints, skip alternatives and saved personal progress. Add a preview and a paid quest unlock with verified access. Keep story content separate from user progress and enforce paid content access appropriately. Do not require location tracking, restricted access or public multiplayer features for the first version.
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
- Leave a quest halfway through, sign in again and confirm that progress resumes at the correct branch.
- Mark a stop unavailable and verify that the alternative still leads to a coherent ending.
- Attempt to open a paid chapter without the required purchase and confirm that access is checked beyond a cosmetic button state.
Test the story on a short walk with volunteers and observe where they lose interest or need help. Compare completion and recall with a plain list of locations. The next improvement may be better writing or route pacing, rather than a more complicated algorithm.
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 the first version need GPS?
No. A route description and user-confirmed progress can demonstrate the experience. Add location features only if they improve a specific part of the journey.
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.