React Native / Mapping Developer Needed to Finish Existing Oversize Permit Navigation App

React Native / Mapping Developer Needed to Finish Existing Oversize Permit Navigation App Existing Working Project — 2-Week Target — $1,800 Fixed Price We have an existing, functioning application called URoute for the oversize/overweight trucking industry. THIS IS NOT A PROJECT STARTING FROM SCRATCH. A substantial portion of the application and routing system has already been developed and tested. We are looking for an experienced developer who can review the existing codebase, preserve what works, complete the production system, build/finish the mobile applications, and get URoute approved for distribution on both the Apple App Store and Google Play Store. Budget $1,800 fixed price Three milestones of $600 each. Target Schedule Approximately 2 weeks for development completion and submission to both app stores. Apple and Google control their own review timelines, but the developer will remain responsible for resolving reasonable application-related review/rejection issues until both applications are approved. ⸻ WHAT ALREADY EXISTS URoute is not a concept or blank-slate development project. Existing work includes: * Working permit upload/extraction process * AI/API-based permit parsing * Existing API access/key for permit parsing * Parsing system already tested successfully with real permits * Existing state-specific permit parsing/profile work * Route extraction from permits * Mapping and route display * Valhalla integration already developed and running * State-border crossing handling * Existing frontend * Existing Node/Express backend * Backend/API security work already started * Sensitive API credentials moved out of the frontend and into backend environment configuration The developer is expected to evaluate and build upon the existing system before proposing replacement of working components. We are NOT looking for someone to discard the existing application and rebuild the entire project from scratch. Production security still needs to be reviewed and completed, including appropriate authentication, database permissions, secure permit storage, deployment configuration and access controls. ⸻ CRITICAL ROUTING REQUIREMENT This is the most important requirement of the project. URoute does NOT determine what route an oversize/overweight load should take. The state-issued permit is the authority. URoute’s job is: Permit → Extract authorized route → Interpret permit instructions → Map that exact route → Guide the driver along the permitted route URoute is NOT a route-planning system for determining where an oversize load should travel. The permitting authority has already made that determination. URoute must NOT: * Calculate routes based on load height * Calculate routes based on load width * Calculate routes based on load weight * Calculate routes based on load length * Use load dimensions to determine another route * Optimize the permitted route * Recommend a shorter route * Recommend an alternative truck route * Substitute a route because Google, Mapbox, Valhalla or another mapping provider prefers it * Guess when the permit route cannot be confidently interpreted There will be NO load-dimension-based routing in URoute. URoute is designed to accurately interpret and navigate the route stated on the government-issued permit — not rewrite the permit or independently determine whether another road is suitable for the load. If URoute cannot confidently interpret or map part of the permitted route, the application must place that route or section on: HOLD / NEEDS REVIEW rather than guess or substitute another route. ⸻ PERMIT EXTRACTION — IMPORTANT Permit formats vary greatly from state to state and also vary according to how the permit is received. This is a significant part of the project. URoute must be capable of processing permits received in different forms, including: * Native/digital PDF permits with selectable text * Scanned PDF permits * Photos/images of permits * Multi-page permits * Route tables * Written route paragraphs * Abbreviated highway/road routing instructions * Permits where the actual route occupies only a small portion of the document * Permits containing substantial legal provisions, restrictions and boilerplate that must NOT be interpreted as driving directions * Routes containing ramps * Frontage roads * Bypasses * Detours * Highway transitions * State-line transitions Permit layouts and terminology can vary substantially between states. Some states provide relatively clean structured routing tables. Others may provide dense written routing instructions. Still others may mix a relatively short permitted route with multiple pages of provisions, restrictions and other information that are not part of the driving route. The system must identify and extract the route actually authorized on the permit without treating unrelated permit provisions as routing instructions. Where states use similar permit formats, shared extraction logic is encouraged. We do NOT want unnecessary duplication simply to create a separate parser for every state. State-specific rules/profiles should be used where they are actually necessary. ⸻ EXISTING AI/API PERMIT PARSING URoute already has an AI/API-based permit parsing system integrated into the existing codebase. The necessary API access/key is already available. The existing parsing approach has been tested successfully with real permits. The developer is NOT being asked to create a new AI permit-reading system from scratch. The objective is to build upon and improve the existing working extraction pipeline, including state/permit-format-specific rules where necessary. The developer should first evaluate the existing implementation before proposing replacement of any working parsing component. If the system cannot confidently determine the permitted route, it must return: HOLD / NEEDS REVIEW rather than guess. ⸻ STATE COVERAGE Target coverage is the Lower 48 United States. Several state permit parsers/profiles already exist. We do NOT necessarily require 48 completely independent parsers. Developers are encouraged to reuse extraction logic among states with similar permit formats and add state-specific rules only where necessary. The goal is reliable, maintainable architecture rather than unnecessary duplication. Success is measured by correctly interpreting real state-issued permits and accurately mapping the route specified on those permits. Simply having a parser labeled for each state does not constitute successful completion. ⸻ MOBILE APPLICATION The production mobile application should use React Native and support: * iPhone * iPad * Android phones * Android tablets Mobile functionality includes: * User account/login * Permit upload * Permit storage * Permit route extraction * Map display * GPS driver location * Guidance along the permitted route * Route deviation detection * HOLD / NEEDS REVIEW functionality * Appropriate offline capability for drivers traveling through areas with poor or no cellular service * Secure production API configuration * Synchronization with the user’s other devices Mobile phones and tablets will be the primary platforms used by drivers while traveling. ⸻ WINDOWS PC & APPLE MAC URoute must also be available from: * Windows PCs * Apple Mac computers A production web/PWA interface is preferred for Windows and Mac. Separate native Windows and Mac applications are NOT required. The desktop/web version must share the same: * Backend * Database * User accounts * Permits * Extracted routes * Saved mapping information A user should be able to: * Upload a permit from a PC or Mac * Process the permit * View the extracted permitted route on a larger map * Review the route before travel * Correct or add a mapping point when necessary without changing the underlying permitted route * Save the route * Open the same permit and route on an iPhone/iPad or Android device Changes must synchronize between desktop and mobile devices through the user’s account. For example: A permit processed and reviewed on a Windows PC should be available to the driver on their phone/tablet without having to recreate the route. ⸻ MAPPING / NAVIGATION The existing system uses Valhalla. For the mobile mapping/navigation layer, Mapbox is preferred, although Google Maps may be proposed if the developer can explain why it provides a better technical solution for this particular application. We are open to an experienced mapping developer’s recommendation. However, this requirement is NON-NEGOTIABLE: The mapping/navigation system must follow the route extracted from the state-issued permit. It cannot independently reroute the driver onto a route that conflicts with the permit. If Google Maps, Mapbox, Valhalla or another mapping system would normally prefer another road, URoute must preserve the permitted route. ⸻ MILESTONE 1 — $600 Existing System → Production Backend * Review existing URoute codebase * Preserve functioning existing code * Confirm existing permit parsing/extraction pipeline * Productionize existing backend * Deploy/host existing Valhalla implementation * Database * User accounts/authentication * Permit upload and storage * Review and production-harden existing API/backend security * Secure API keys/configuration * Existing permit-to-route pipeline functioning on hosted infrastructure * Expand and test state permit support Milestone payment is released when the agreed functionality is demonstrated working. ⸻ MILESTONE 2 — $600 Mobile Applications + Desktop Synchronization * React Native iOS application * React Native Android application * Connect mobile applications to URoute backend * Permit upload from mobile devices * Display extracted permitted route * GPS/location functionality * Permitted-route guidance * Route deviation detection * HOLD / NEEDS REVIEW functionality * Offline capability * Windows/Mac web/PWA functionality * Synchronization between mobile and desktop * Continue state permit testing and coverage Milestone payment is released when the agreed functionality is demonstrated working on actual devices. ⸻ MILESTONE 3 — $600 Lower 48 + Production Launch * Lower 48 permit support completed and tested * Production testing * Testing with real permit examples * iPhone/iPad testing * Android phone/tablet testing * Windows PC web/PWA testing * Mac web/PWA testing * Cross-device synchronization testing * Bug fixes * Production deployment * Apple App Store submission * Google Play Store submission * Address reasonable application-related App Store and Google Play review/rejection issues * Complete source code transferred to owner * Deployment/configuration documentation * Final handoff ⸻ APP STORE APPROVAL IS REQUIRED This is a non-negotiable project requirement. Final project completion requires the mobile applications to be approved for distribution by BOTH: * Apple App Store * Google Play Store Development and submission should be completed within the approximately 2-week target. We understand Apple and Google control their own review schedules. Review time outside the developer’s control will not itself constitute failure to meet the development deadline. However, the developer must remain responsible for promptly addressing reasonable application-related issues identified during store review until both applications have been approved. ⸻ REQUIRED PRODUCTION PLATFORMS Final system must provide: ✓ iPhone/iPad application ✓ Android phone/tablet application ✓ Windows PC web/PWA access ✓ Apple Mac web/PWA access ✓ Shared user accounts ✓ Synchronized permits and routes across devices ✓ Apple App Store approval ✓ Google Play Store approval ⸻ SCHEDULE & BUDGET Fixed-price project: $1,800 Three milestones: Milestone 1 — $600 Milestone 2 — $600 Milestone 3 — $600 Target: Approximately 2 weeks for development completion and submission to both app stores. We are looking for someone who can make this project a priority. Again, this is an existing functioning project. We are specifically looking for someone capable of understanding and continuing an existing codebase rather than unnecessarily rebuilding the application. ⸻ WHEN APPLYING Please do NOT send a generic mobile-app proposal. Please answer each of the following questions: 1. Have you personally built React Native applications that were approved and published on both the Apple App Store and Google Play Store? 2. Please provide examples of applications you personally worked on that are currently or were previously available in those stores. 3. What experience do you have with Mapbox, Valhalla, Google Maps, GPS/navigation or route-matching applications? 4. How would you make a navigation application follow an exact predetermined route rather than allowing Google Maps, Mapbox or another mapping provider to reroute the driver? Please be specific. 5. How would you approach offline navigation for drivers who may temporarily lose cellular service? 6. Are you comfortable reviewing and continuing an existing codebase instead of rebuilding the application? 7. How would you approach permit extraction across the Lower 48 without unnecessarily creating 48 completely independent systems? 8. How would you design or improve the existing extraction system to reliably handle: * Digital PDFs * Scanned PDFs * Permit images * Route tables * Written route paragraphs * Multi-page permits * Permits where routing instructions are mixed with several pages of unrelated provisions? 9. The existing AI/API permit parser and Valhalla integration are already working. How would you evaluate the existing implementation before deciding whether anything needs to be replaced? 10. Can you commit to making this project a priority and targeting approximately 2 weeks for development completion and store submission? 11. Are you comfortable with the $1,800 fixed budget divided into three $600 milestones? 12. Are you willing to address reasonable application-related Apple App Store and Google Play review issues until both applications are approved? ⸻ IMPORTANT APPLICATION INSTRUCTION Begin your proposal with the words: PERMIT ROUTE This tells us you have read and understand the project requirements. Generic proposals that do not answer the questions above will not be considered.