Graduation Project: A Travel Photography Light Planner

The app and the problem it solves

A traveller may want a sunrise view, a softly lit street and an evening waterfront scene on the same day. Those wishes can conflict with distance, access hours and changing light. LightRoute helps turn them into a feasible photography plan, making it an unusual but practical graduation project for students in Egypt.

The first version can use manually entered light windows and reviewed sample data. The core is scheduling visits within those windows, not predicting the weather or generating pictures. That keeps the demonstration achievable while leaving a meaningful path toward astronomical calculations later.

The first user journey

1. The user adds a small set of photo locations with desired light windows, visit duration and known access hours.
2. They enter travel times between locations and identify any stop that matters more than the others.
3. The app finds a feasible sequence or explains which location conflicts with the available time.
4. The photographer saves an alternative plan for changed conditions and exports a concise schedule to carry during the day.

The logic that makes the project distinct

A visit must fit inside the intersection of the desired light window and the location’s access window. A following visit must also allow travel time from the previous stop. For a small route, enumerate possible orders and keep the feasible ones, then rank them by the user’s stated priorities.

If you add calculated solar position later, use a documented method and correct location, date and time-zone inputs. NOAA’s solar resources document azimuth and elevation, although its calculator is no longer actively maintained; validate any implementation independently. Solar geometry alone does not predict cloud cover, shadows from buildings or whether a viewpoint is open. Preserve those as separate observations or unknowns.

usable window = desired light window ∩ access window
next start ≥ previous finish + travel time
A visit must finish before its usable window closes.

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:

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 saved multi-day photo plans or an export that compares two route options. Original local photo itineraries could become a separate content product if access and source details are maintained. The app sells planning help; it should not promise a particular photograph, clear sky or access to a restricted viewpoint.

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.

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.

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 06:30 start example and reject the visit that finishes after its usable window.
• Make two windows disjoint and explain why no sequence can satisfy both with the supplied travel time.
• Close a viewpoint for the selected date and ensure that attractive light does not override the access constraint.

Compare a manually chosen route with the app’s feasible schedules and ask photographers whether the explanation matches how they plan. Later, validate solar calculations against an independent reference before replacing user-entered windows. Weather integration should remain a separate, timestamped source.

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.

Must the project calculate sunrise and sunset itself?

No. User-entered or reviewed sample windows are enough to demonstrate the scheduling problem. A validated solar-position module can be a later extension.

Sources and next steps

• NOAA: solar position calculator
• Gammal Tech: build a website with AI
• Gammal Tech: backend, login and payment reference

Recheck sources and service terms when implementing. Fictional data and prices in this article illustrate the project, rather than current offers.