Hackathon prototype · 2026 · Prototype
Mangystau Trials
A travel-planning prototype for the Mangystau region, built during a hackathon. It did not reach the final.
- Prototype, not a finished product
- Deployed and reachable
- Source on GitHub
Overview
The user sets a budget, trip length, interests, and transport. The prototype returns a route with locations, estimated time, and basic trip information, with the map and the location list in the same order.
Context
The project started during a hackathon, with limited time to explain the idea, build the main flow, and show how a route responds to different travel preferences. The idea was larger than the schedule from the first hour.
The problem
Planning a trip across Mangystau means deciding on time, transport, interests, and budget at once. Our first version tried to support all of that before the route flow itself worked.
The system, step by step
- Budget, days, interests, transport
- One route is ordered from those inputs
- The map reads that route
- The location list reads the same route
- Map and list share one order
Architecture
Trip setup and route output in one flow
- Next.js
- React
- TypeScript
Destinations typed and ordered by the trip preferences
- TypeScript
Destinations shown in the same order as the list
- Map interface
Deployed so the prototype stays reachable
- Vercel
Key decisions
Question
What is the single output of this product?
The route. Everything else is input to it.
We reached that answer too late. Naming the one output earlier is what would have kept the scope inside the time we had.
Question
How should the map and the list relate?
One shared order between map markers and location cards.
Two orderings of the same trip would make the user translate between them instead of reading a plan.
What I built
A trip setup grouped into one short step, and a route output with locations, estimated time, and basic trip details. I worked on the idea, the page structure, the user flow, the route interface, the map, and the frontend.
What went wrong
The scope grew faster than the time available. Map work and route detail took attention away from proving the main planning flow while it still could have changed the result.
Outcome
Result
The project did not reach the hackathon final. A working prototype is still deployed, but it does not support every part of complete trip planning.
What I learned
Define the main feature before adding supporting ideas. A smaller route demo would have explained the project better in the time we had.
Stack
- Next.js
- React
- TypeScript
- Map interface
- Vercel