Taxi App Developer - Bug Fixes & Publishing

Senior Mobile / Full-Stack Developer – Taxi App Bug Fixes, MapTiler, GPS, Location Search & App Publishing We have an existing taxi/private-hire platform with: * Customer mobile app * Driver mobile app * Dispatcher system * Operator/Admin portal * Backend/API * Real-time booking and dispatch * GPS/live tracking * Pricing * Notifications * Scheduled and ASAP bookings We already have 2 developers working on the project. We need an additional experienced developer to review the existing codebase, fix current bugs, improve stability, resolve location/map issues, test the full booking flow and help publish the mobile apps to the Apple App Store and Google Play Store. This is NOT a new project and NOT a rebuild from scratch. We have an existing bug list which will be provided. Main Responsibilities You will be required to: * Review existing source code and architecture * Work alongside our current developers * Reproduce and fix existing bugs * Identify root cause rather than temporary patching * Test fixes across connected modules * Improve mobile app stability and performance * Fix GPS/location problems * Review backend/API issues where required * Complete production builds * Assist with Apple App Store publishing * Assist with Google Play publishing * Provide evidence for every completed task IMPORTANT – MapTiler / MapLibre We are using MapTiler / MapLibre, not Google Maps wherever technically possible. You should have experience with: * MapTiler * MapLibre * OpenStreetMap * Geocoding * Reverse geocoding * Address autocomplete * GPS coordinates * Map markers * Routes * Live location * Pickup/drop-off selection * Distance calculations Do not replace MapTiler with Google Maps without prior approval. We want to keep third-party mapping/API costs under control. VERY IMPORTANT – Intelligent Local Location Suggestions Our location search must understand where the customer is. Example: Customer is in Chesterfield and types: Tesco The system should show nearby Chesterfield Tesco locations first. It should NOT show Tesco London, Glasgow or other distant locations before relevant local results. If customer types: Train Station Chesterfield Railway Station and nearby stations should appear first. If customer searches: McDonald’s Nearby branches should appear first. However, the customer must still be able to search for a distant specific destination. Example: Customer in Chesterfield types: Heathrow Terminal 5 The system must correctly return Heathrow Airport Terminal 5 even though it is far away. The search system therefore needs: LOCAL RELEVANCE + SEARCH INTENT not simply global search results. Suggested Location Ranking Search results should consider: 1. Customer GPS location 2. Pickup location 3. Current town/city 4. Operator service area 5. Distance 6. Exact text match 7. Place category 8. Search relevance 9. Previous searches/bookings 10. Frequently selected destinations 11. Operator-defined preferred locations Example scoring concept: Location Score = Text Match + Proximity + Local Relevance + User History + Popularity Developer may propose a better technical approach. Search Radius Logic Search should expand intelligently. Example: * First search nearby area * Then wider local area * Then regional * Then national if required But a specific search such as Heathrow Airport must still work immediately. Location Types Search should properly support: * Residential addresses * Postcodes * Streets * Airports * Airport terminals * Railway stations * Bus stations * Hotels * Hospitals * Universities * Schools * Supermarkets * Restaurants * Shopping centres * Businesses * Car parks * Tourist attractions * Stadiums * Event venues * Landmarks Search result display should ideally include: Place name Street/area Town/city Postcode Distance where available Search Performance Autocomplete should be fast and cost-efficient.

Requirements

* Debounce API requests * Avoid unnecessary API calls * Cache repeated searches where appropriate * Remove duplicate results * Prioritise relevant results * Handle weak GPS * Handle denied location permissions * Handle internet failure * Allow manual address entry * Prevent blank/loading screens Saved / Recent Locations Where applicable support: * Home * Work * Favourite places * Recent searches * Previous destinations * Previous pickup locations * Frequently used addresses These may also improve search ranking. Pickup / Destination Map Review and fix: * Current location detection * Pickup pin * Destination pin * Map dragging * Address after moving pin * GPS accuracy * Search result to map coordinates * Coordinates to address * Map zoom * Map centring * Route display * Distance calculation * Postcode searching The latitude/longitude stored in each booking must match the selected address. Driver Live Tracking Review: * Driver GPS updates * Customer driver tracking * Dispatcher tracking * Background location * Battery usage * GPS reconnect * Location permissions * Incorrect/jumping markers * Loss of signal handling Bug Fixing Process For every bug: 1. Reproduce issue 2. Identify root cause 3. Fix issue 4. Test locally 5. Test API interaction 6. Test connected modules 7. Regression test 8. Provide screenshot/video evidence 9. Commit through Git 10. Only mark complete after successful testing A task is NOT complete just because code has been changed. API / Backend Review relevant issues involving: * Authentication * Booking * Driver * Customer * Dispatch * Pricing * Location * Notifications * Payments * Operator/Admin Check for: * Failed APIs * Incorrect payloads * Duplicate requests * Timeouts * Authentication issues * Incorrect database updates * Duplicate bookings * Validation problems Mobile App Testing Check: * Crashes * Freezing * Slow loading * Blank screens * Infinite loaders * Navigation * Login/logout * Push notifications * Location permissions * GPS * Camera/uploads * Background behaviour * Different Android/iPhone screen sizes Real-World Test Example Customer in Chesterf