Remix

Make your own version of Wayfinder Navigation

Get an exact, working copy in your account, then change anything with chat.

Original by luqman luqqus

What would you change?

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

# PROJECT: BUILD A COMPLETE SMART NAVIGATION APP LIKE WAZE AND GOOGLE MAPS

Act as a professional mobile app developer, navigation engineer, mapping specialist, backend developer, and UI/UX designer.

Build a fully functional, modern navigation application inspired by the best features of Google Maps and Waze. Give the app its own unique name, branding, icons, and design.

The application must help users find destinations, calculate fast and safe routes, navigate using live GPS, monitor traffic, receive voice directions, report road hazards, add multiple stops, and discover nearby places.

**IMPORTANT:** This project must be designed primarily as a genuine smartphone app. Do not simply create a desktop website and shrink it to mobile size. Prioritize mobile usability, reliable navigation, road safety, speed, and a clean interface.

Use real mapping, routing, GPS, traffic, and backend services wherever available. Do not create fake traffic, simulated GPS, invented road information, or buttons that do nothing.

# 1. MOBILE-FIRST APP DESIGN

Build a professional mobile interface designed primarily for Android and iPhone.

Requirements:
- Full-screen interactive map.
- Large, easy-to-tap buttons.
- Floating current-location and report buttons.
- Bottom navigation for Map, Explore, Saved Places, Reports, and Profile.
- Search bar at the top.
- Bottom sheets for destinations, route choices, and journey details.
- Minimal interface during active navigation.
- Light mode, dark mode, and a dedicated nighttime navigation theme.
- Support different phone screen sizes and orientations.
- Smooth animations without unnecessary effects.
- Fast loading and efficient memory, battery, and data usage.
- Clear text, recognizable icons, and accessible colours.
- Safe layouts that avoid covering essential map information with buttons.
- Proper handling of mobile keyboard, GPS permissions, notifications, and audio.

During navigation, prioritize the map, next turn, remaining distance, estimated arrival time, and voice instructions.

Do not show unnecessary menus or advertisements over critical navigation information.

# 2. INTERACTIVE MAP AND LIVE GPS LOCATION

Integrate a real mapping service, such as Mapbox, or another suitable provider.

The map must display real roads, streets, highways, bridges, tunnels, intersections, roundabouts, landmarks, and place names wherever the provider supports them.

Implement:
- Live device GPS location.
- A moving position marker.
- Direction-of-travel indicator.
- Automatic map following while navigating.
- Rotating navigation view with a north-up option.
- Zoom and map recenter controls.
- Current location accuracy information where available.
- Current speed when supported.
- Destination selection by tapping the map.
- Search for addresses and places.
- GPS permission handling.
- Graceful recovery from weak GPS signals.
- Clear indication when location information is unavailable or outdated.

Never use a fixed marker as a substitute for live GPS.

# 3. ROUTE FINDER AND DESTINATION SEARCH

Allow users to:
- Enter a starting location.
- Use their current location as the starting point.
- Search for destinations by name, address, landmark, business, or coordinates.
- Select suggested search results.
- Choose a destination directly on the map.
- Use voice search where supported.
- Reverse the starting point and destination.
- Add intermediate stops.
- Save favourite places.
- View recent destinations.
- Share destinations and routes.
- Preview the route before starting navigation.

Show route options with:
- Distance in kilometres.
- Estimated travel duration.
- Estimated arrival time.
- Traffic conditions when available.
- Road types and major roads.
- Toll information where supported.
- Road closures and restrictions when verified.
- Important warnings.

Highlight the recommended route and explain why it is recommended.

# 4. FASTEST ROUTE AND INTELLIGENT ROUTE CALCULATION

Prioritize the fastest practical and legal route rather than simply choosing the shortest distance.

Use a routing service that supports traffic-aware route calculation where available.

Consider:
- Current traffic.
- Estimated travel time.
- Accidents and road incidents.
- Construction and roadworks.
- Road closures.
- Turn restrictions.
- Legal road access.
- Vehicle restrictions.
- Toll preferences.
- Avoid-highway preferences.
- Avoid-toll preferences.
- Road conditions supported by the provider.

Display alternative routes when available:
1. Fastest practical route.
2. Alternative route with less traffic.
3. Shortest practical route.

Do not display an alternative unless it has actually been calculated.

Automatically suggest a faster route when updated information shows a meaningful time saving. Explain the estimated time saved before rerouting when appropriate.

Avoid unnecessary detours through complicated airport entrances, terminals, parking areas, service roads, private roads, pedestrian areas, and restricted facilities.

When navigating to an airport, allow users to choose the correct terminal, arrivals, departures, parking area, or another accessible destination when the mapping data supports it.

Never invent shortcuts or claim a route is fastest without reliable route calculations.

# 5. TURN-BY-TURN NAVIGATION

Implement real navigation along the selected route.

Display:
- Next turn and direction.
- Distance to the next turn.
- Current road name.
- Upcoming road name when available.
- Total distance remaining.
- Estimated time remaining.
- Estimated arrival time.
- Current speed where supported.
- Speed limit where reliable data is available.
- Lane guidance where supported.
- Highway exits and junction information.
- Roundabout instructions where supported.
- Distance to the next stop.
- Final destination.

Provide spoken instructions such as:
- "In 500 metres, turn right."
- "Keep left to take the exit."
- "At the roundabout, take the second exit."
- "Continue straight for 2 kilometres."
- "You have arrived at your destination."

Allow users to:
- Mute and unmute navigation.
- Adjust voice volume.
- Choose available voice languages.
- Replay the last instruction.
- Pause and resume navigation.
- End the journey.
- Change the destination.
- Add or remove stops.
- Switch between route overview and navigation.
- Enable or disable automatic rerouting.

Detect missed turns and calculate a new legal route using the current location. Do not continue giving instructions for an outdated route.

# 6. LIVE TRAFFIC INFORMATION

Integrate a real traffic-data provider.

Display traffic conditions using clear road colours according to the provider's conventions.

Suggested colours:
- Green: flowing traffic.
- Orange: moderate congestion.
- Red: heavy congestion.
- Dark red: severe congestion, where supported.

Show available information about:
- Traffic congestion.
- Accidents.
- Roadworks.
- Road closures.
- Disabled vehicles.
- Blocked lanes.
- Flooding.
- Road hazards.
- Traffic delays.
- Estimated delay duration.
- Incidents ahead.
- Alternative routes.

Update information according to the provider's permitted update frequency.

Display the last update time when available.

If live traffic information is unavailable, clearly label it as unavailable. Never generate fake live traffic.

# 7. COMMUNITY REPORTING BUTTON

Add a prominent report button that is accessible from the map and navigation screens.

Users must be able to report:
- Accidents.
- Heavy traffic.
- Road closures.
- Roadworks.
- Broken-down vehicles.
- Objects on roads.
- Dangerous road conditions.
- Flooding.
- Potholes.
- Blocked lanes.
- Temporary obstructions.
- Incorrect map information.
- Temporary speed restrictions.
- Other road hazards.

Use large category buttons with clear icons.

When a report is submitted:
- Capture the location when permission is available.
- Record the category and submission time.
- Associate it with the relevant road when possible.
- Allow an optional description.
- Save it to a persistent backend.
- Confirm submission only after it succeeds.
- Display reports on the map with appropriate labels.
- Expire old reports according to configurable rules.

Allow users to confirm whether a hazard is still present.

Implement spam prevention, duplicate detection, report moderation, rate limits, and reporting of false information.

Label community reports as unverified until appropriately confirmed.

Detailed reporting must not encourage drivers to type while moving. Encourage users to stop safely or use permitted hands-free quick-report features.

# 8. POLICE AND ROAD ENFORCEMENT INFORMATION

Provide a road-safety information layer for:
- Officially published speed-camera locations.
- Officially published enforcement zones.
- Police-related road closures.
- Official traffic-control points where public information is available.
- Emergency traffic restrictions.
- Official road safety announcements.

Use lawful, public, and appropriately licensed sources.

Never invent police locations or claim to provide live police tracking without an authorized, reliable data source.

Where community reports are legally permitted, clearly label them as unverified reports rather than confirmed police activity.

Provide audio warnings only when reliable information and applicable laws permit them.

Do not encourage speeding, evading law enforcement, or violating traffic rules.

# 9. ROAD MARKINGS, LANES, AND ROAD SAFETY

Display road information accurately using the mapping provider's available data.

Support road features such as:
- Solid white lines.
- Broken white lines.
- Solid and broken line combinations.
- Double solid lines.
- Lane arrows.
- Merge lanes.
- Exit lanes.
- Bus lanes.
- Bicycle lanes.
- Pedestrian crossings.
- Stop lines.
- Give-way markings.
- Roundabouts.
- One-way roads.
- Reversible lanes.
- Restricted turns.
- Emergency stopping areas.
- Road shoulders.
- Speed limits.
- School zones.
- Temporary road markings.

Show lane guidance before complex intersections and highway exits when reliable data is available.

Do not guess whether a road marking is solid or broken if that information is unavailable.

Add an optional road-safety learning section explaining common markings and traffic rules.

For UAE users, prioritize officially published UAE traffic rules and applicable emirate-specific regulations.

Never instruct users to cross prohibited solid lines, enter restricted lanes, or break traffic laws.

# 10. VOICE NAVIGATION AND SOUND ALERTS

Implement a complete audio settings section.

Include:
- Spoken turn-by-turn directions.
- Upcoming-turn warnings.
- Rerouting announcements.
- Destination arrival announcements.
- Traffic delay warnings.
- Road closure warnings.
- Hazard alerts.
- Supported speed-limit alerts.
- Adjustable voice volume.
- Mute, voice-only, and voice-plus-sound modes.
- Available voice and language options.
- Replay-last-instruction button.
- Voice search where supported.

Use natural, short, understandable instructions.

Avoid excessive or repetitive alerts.

If voice reporting is supported, require clear confirmation before submitting reports.

Ensure audio instructions remain useful while other audio is playing, subject to platform capabilities.

# 11. DISTANCE, SPEED, AND ARRIVAL INFORMATION

Display:
- Distance to the next turn.
- Distance to the next stop.
- Total distance remaining.
- Current speed where supported.
- Applicable speed limit where reliable.
- Time remaining.
- Estimated arrival time.
- Current road name.
- Traffic delay.
- Total journey distance.
- Estimated time saved through rerouting.

Allow users to select kilometres or miles.

Update the estimated arrival time as the route and traffic conditions change.

Clearly identify estimates as estimates, not guaranteed arrival times.

# 12. NEARBY PLACES AND POINTS OF INTEREST

Allow users to search for nearby:
- Petrol stations.
- Electric vehicle charging stations.
- Parking areas.
- Hospitals.
- Pharmacies.
- Restaurants.
- Grocery stores.
- Mosques.
- ATMs.
- Public toilets.
- Airports and terminals.
- Hotels.
- Vehicle repair shops.
- Service centres.
- Rest areas.

Show available information such as:
- Distance.
- Estimated travel time.
- Opening hours.
- Address.
- Contact details.
- Ratings where provided by a legitimate source.

Allow users to select a place and add it to their existing journey as a stop.

Do not invent business information, opening hours, ratings, or availability.

# 13. MAP LAYERS AND DISPLAY SETTINGS

Offer supported map layers:
- Standard road map.
- Satellite imagery.
- Live traffic.
- Community incidents.
- Road closures.
- Parking.
- Points of interest.
- Terrain.
- Public transport where available.
- Legally permitted speed-camera information.

Allow each layer to be switched on or off independently.

Ensure the navigation route and driving instructions remain readable on every map style.

# 14. OFFLINE MAPS AND WEAK INTERNET SUPPORT

Where supported by the mapping provider and licensing:
- Allow users to download maps for selected areas.
- Cache relevant map tiles and route information.
- Preserve the active destination and route when possible.
- Handle temporary internet loss gracefully.
- Continue GPS positioning when supported.
- Display the last known location when appropriate.
- Clearly identify features that require an internet connection.

Do not claim that live traffic or new community reports remain available offline.

# 15. USER ACCOUNTS AND PERSISTENT DATA

Provide optional secure accounts.

Users should be able to:
- Save favourite destinations.
- Save Home and Work.
- View recent searches.
- Save journeys.
- Synchronize supported preferences.
- Manage languages and sound settings.
- Review their submitted reports.
- Manage privacy settings.
- Delete their account and associated data where required.

Use a persistent backend database rather than temporary browser storage for data that must survive sessions.

Implement secure authentication, database permissions, input validation, and protection against unauthorized access.

Allow basic map exploration without forcing account creation when possible.

# 16. UAE-SPECIFIC NAVIGATION

Make the United Arab Emirates the initial supported region.

Prioritize accurate roads, addresses, place names, and routing in Dubai, Sharjah, Abu Dhabi, and other UAE emirates.

Support:
- Arabic and English interfaces.
- Right-to-left Arabic text.
- UAE-relevant road names and destinations.
- Kilometres by default.
- UAE-relevant speed limits and road restrictions where reliable data is available.
- Toll-road information where supported.
- Official traffic alerts.
- Airport terminals and accessible drop-off or parking locations.
- UAE-specific road markings and traffic rules.
- Location search using Arabic or English names.

Use reliable official sources for traffic rules and road restrictions.

Do not assume that every emirate has identical traffic conditions, road rules, or toll arrangements.

# 17. MULTIPLE STOPS AND MULTI-DESTINATION ROUTING

Build a complete multi-stop route planner.

Users must be able to:
- Add multiple stops between the starting location and final destination.
- Search for an address, landmark, business, or place and add it as a stop.
- Add petrol stations, charging stations, restaurants, mosques, parking areas, hospitals, supermarkets, and other useful places.
- Add stops by tapping the map.
- View all stops in an organized list.
- Drag and drop stops to change their order.
- Edit, replace, or remove stops.
- Mark stops as required or optional.
- See the distance and estimated travel time to each stop.
- See total journey distance, total estimated duration, and final arrival time.
- Recalculate the complete route when stops change.
- Skip a stop and continue to the next destination.
- Save and reuse multi-stop journeys.
- Share the itinerary with other people.
- Hear spoken announcements for upcoming stops.
- View the next stop and final destination during navigation.

Provide an option to optimize stop order to reduce total driving time, while respecting required stops and user preferences.

Do not reorder stops without the user's permission.

When suggesting a petrol station, charging station, restaurant, or rest stop, calculate the detour distance and additional travel time where possible.

Clearly distinguish the time remaining to the next stop from the time remaining to the final destination.

Use a real routing API that supports multi-stop directions. Never draw straight lines between destinations as a substitute for road routing.

If the provider limits the number of stops, handle that limitation gracefully and explain it.

# 18. INTELLIGENT ROUTE PREFERENCES

Allow users to customize route calculation.

Include preferences such as:
- Fastest route.
- Avoid tolls.
- Avoid highways.
- Prefer major roads.
- Prefer fewer turns where supported.
- Avoid unpaved roads where supported.
- Vehicle type where supported.
- Accessibility-related preferences where supported.
- Preferred units.
- Preferred navigation language.

Explain when a preference may increase travel time or distance.

Never override legal restrictions or road access rules to satisfy a preference.

# 19. ARRIVAL, PARKING, AND DESTINATION DETAILS

When the user approaches the destination:
- Announce the arrival.
- Display the destination name and address.
- Show the remaining distance.
- Provide a map overview of the destination.
- Display available nearby parking where reliable data exists.
- Offer accessible entrances or designated drop-off areas where supported.
- Allow the user to mark the journey as complete.
- Preserve the journey history according to their settings.

For airports and large facilities, distinguish the actual destination from a nearby road entrance or parking area when the provider supports this information.

Do not route drivers into pedestrian-only areas or restricted entrances.

# 20. ACCESSIBILITY AND DRIVER SAFETY

Include:
- Large touch targets.
- Readable text.
- High-contrast navigation instructions.
- Colour choices that remain distinguishable where possible.
- Voice guidance.
- Clear warnings.
- Reduced-motion options.
- Screen-reader support where practical.
- Safe notification handling.

Keep critical driving information simple.

Do not encourage users to operate complicated controls while moving.

Do not display distracting animations or require text entry during active navigation.

# 21. PRIVACY AND SECURITY

Request location permissions only when needed and explain their purpose.

Protect:
- Precise location data.
- Saved destinations.
- Home and Work locations.
- Account details.
- Community reports.
- Journey history.

Use secure API integrations and appropriate backend access controls.

Do not expose private API keys in public client-side code.

Do not collect unnecessary personal information.

Provide controls for location sharing, saved data, and account deletion.

Do not share a user's precise location with other users unless the user explicitly enables a suitable sharing feature.

# 22. BACKEND, APIs, AND REAL FUNCTIONALITY

Choose appropriate services for:
- Interactive maps.
- Geocoding and address search.
- Route calculation.
- Traffic-aware directions.
- GPS location.
- Voice instructions.
- Place search.
- User authentication.
- Persistent database storage.
- Community reports.
- Push notifications where appropriate.

Possible mapping providers include Mapbox, Google Maps Platform, or other suitable services. Choose providers based on coverage, pricing, licensing, mobile support, and required features.

Use the provider's documented APIs and supported features.

Implement proper loading states, error handling, retries, permission handling, and empty states.

Store user-generated reports and saved journeys in a real backend.

Never hardcode fake traffic conditions, fabricated route distances, made-up arrival times, or fake report counts.

Never show a success message when an operation has failed.

If an API key, paid plan, account, or permission is required, explain exactly what is needed and provide clear setup instructions.

Do not expose secrets or privileged credentials in frontend code.

# 23. APP PERFORMANCE AND RELIABILITY

Optimize the application for real smartphones.

Requirements:
- Fast initial launch.
- Responsive search.
- Efficient map rendering.
- Smooth map movement.
- Efficient GPS updates.
- Appropriate caching.
- Network error handling.
- Battery-conscious background location use.
- Reliable route recalculation.
- Stable navigation state.
- Clear recovery from crashes or interruptions where practical.
- Support for mobile app lifecycle changes.
- Graceful handling of incoming calls and audio interruptions.

Avoid unnecessary requests and excessive background processing.

# 24. NOTIFICATIONS AND ALERT MANAGEMENT

Provide configurable notifications for:
- Significant traffic changes.
- Major road closures.
- Important route changes.
- Approaching hazards.
- Journey arrival.
- Saved-route alerts where supported.

Allow users to choose which notifications they receive.

Do not send excessive or misleading notifications.

During active navigation, prioritize audible safety-critical information over low-priority notifications.

# 25. APP TESTING AND QUALITY CONTROL

Before considering the application complete, test:
- GPS permission granted and denied.
- Destination search.
- Route calculation.
- Alternative routes.
- Voice instructions.
- Missed-turn rerouting.
- Live traffic integration.
- Community report submission.
- Report persistence.
- Multiple stops.
- Stop reordering.
- Stop removal.
- Route optimization.
- Arrival-time updates.
- Weak internet connection.
- Dark mode.
- Arabic and English interfaces.
- Small and large phone screens.
- Backend failures.
- Invalid destinations.
- Restricted roads.
- Airport routing.
- Account privacy and permissions.

Fix errors found during testing.

Do not mark a feature as complete if it only has a visual button without a working implementation.

# 26. BUILD AND DELIVERY REQUIREMENTS

Build a polished, working application rather than a static prototype.

Use a mobile-compatible architecture suitable for Android and iOS.

If the chosen platform supports native mobile apps, use that capability. Otherwise, clearly explain whether the output is a mobile web app or progressive web app and what additional work is required for native app distribution.

Provide:
- Complete source code.
- A clear project structure.
- Required environment variable names.
- API setup instructions.
- Database schema and access rules.
- Setup and deployment instructions.
- Testing instructions.
- A list of implemented features.
- A list of features requiring API keys, subscriptions, permissions, or additional configuration.

Build features in a sensible order: map and GPS first, destination search and routing second, navigation and voice third, traffic and reports fourth, and multi-stop routing and advanced features alongside the core routing system.

If a feature cannot be implemented with the selected provider, explain the limitation and offer a realistic alternative.

Do not remove working functionality when adding new features. Do not reset existing user accounts or delete saved data during updates.

# FINAL INSTRUCTION

Create a unique, professional, reliable navigation app that combines intelligent routing, live GPS, traffic-aware directions, voice guidance, community road reports, useful nearby places, and multi-stop journeys.

The app should feel intuitive and responsive on a real smartphone.

Prioritize accurate navigation, safe driving, useful features, privacy, and genuine functionality over decorative design.

Start by implementing the working mobile map, GPS, destination search, route calculation, and navigation interface. Then integrate the remaining features using real services and persistent storage.

Do not pretend that unavailable services are working. Clearly distinguish implemented features, features requiring configuration, and features that the selected providers do not support.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.