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 hotel may describe itself as accessible while providing little information about the route from the station or the entrance. AccessTrail focuses on this information gap. It lets a traveller record the features they need and attach evidence to each segment of a proposed journey.
For a graduation project in Egypt, this offers a useful combination of inclusive design, data provenance and explainable filtering. Build for a specific set of user-selected needs, such as a step-free route and a lift requirement. Avoid reducing all accessibility needs to one universal score.
The first user journey
- The traveller selects the features relevant to them without needing to disclose a diagnosis or medical history.
- They divide a trip into segments, such as station exit, street transfer and accommodation entrance, then add operator links or confirmed details.
- The app marks every required feature as confirmed, not met or unknown, with the evidence date beside it.
- The user sees the unresolved questions for the complete journey, prepares a message to the relevant operator and updates the plan after receiving a response.
The logic that makes the project distinct
Use a three-state model. A missing answer is unknown, not accessible and not inaccessible. A route can be described as meeting its recorded requirements only when every essential feature has suitable confirmation. Even then, show the evidence date and the need to reconfirm time-sensitive services.
Keep the exact requirement visible: entrance width, step-free access, lift availability or a user-defined feature. Do not infer usable access from a generic label or photograph alone. AI can help phrase questions from the user’s checklist, but it should not invent measurements or operator assurances.
For each essential feature: confirmed / not met / unknown Journey review = all required features across all segments, with dated evidence.
A classroom demonstration
A sample itinerary contains three segments. The station exit and hotel entrance have dated confirmation of the selected requirement, while the connecting shuttle has no answer. The result is two confirmed segments and one unresolved segment. It must not become a reassuring 67% accessibility badge that hides the gap in the only available transfer.
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 |
|---|---|
| Requirements | User-selected features, priority and optional dimensions. |
| Segments | Location, transport or venue, and the features needed there. |
| Evidence | Source, confirmation text, review date and unresolved questions. |
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 produce a structured journey evidence pack with alternatives and printable operator questions. Begin with personal planning, then explore professional travel-planning use after testing with relevant users. Payment buys organisation and reporting, not a guarantee that a facility will operate as expected.
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 AccessTrail as an inclusive travel graduation project in Egypt. Focus on user-selected accessibility requirements and dated evidence for each route segment. Design an unknown state that cannot be mistaken for confirmation. Suggest a small paid evidence pack and a user study that measures whether travellers notice unresolved essential details.
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 AccessTrail with a responsive English frontend, backend, database, authentication and payments. Add personal requirements, journey segments and dated evidence records. Use confirmed, not met and unknown states, with essential unresolved features at the top. Save plans privately and add a paid printable evidence pack. Generate operator questions from recorded gaps, without inventing measurements or promising accessibility.
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 one essential transfer feature unknown and confirm that the full journey is not labelled confirmed.
- Update an evidence date and ensure the report shows the new date while retaining the user’s requirement.
- Change a feature from optional to essential and verify that the journey review changes immediately.
Evaluate the interface with people who use the relevant accessibility features, and let them define what makes evidence useful. A successful project makes unknowns easier to act on. A later version could add operator-maintained information once responsibility for keeping it current is agreed.
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 collect a traveller’s medical information?
The proposed version needs functional preferences and journey details. It can work without diagnoses, medical records or explanations of why a feature is needed.
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.