The KiloDrive mobile foundation and its retained early release history.
Release overview
KiloDrive 1.0.0+1 retains the foundational release together with the reviewed build 89 and build 109 histories. Original summaries, structured improvements and governance evidence remain available under this release.
Improvements in this release
Des appels, un chat et des commandes de trajet plus fiables.
Les appels entrants sont désormais récupérés lorsqu’une notification en temps réel est retardée, les messages du chat sont confirmés après leur acceptation durable, les détails du trajet restent accessibles sur les écrans étroits et avec du texte agrandi, et le statut de paiement d’un trajet en espèces annulé reste synchronisé pour le passager et le conducteur. Les protections de vérification des conducteurs restent actives.
What this means for you: Des appels, un chat et des commandes de trajet plus fiables.
Llamadas, chat y controles de viaje más confiables.
Las llamadas entrantes ahora se recuperan si una notificación en tiempo real se retrasa, los mensajes de chat se confirman después de su aceptación segura, los detalles del viaje siguen disponibles en pantallas estrechas y con texto grande, y el estado de pago de un viaje en efectivo cancelado se mantiene sincronizado para pasajeros y conductores. Las protecciones de verificación de conductores permanecen activas.
What this means for you: Llamadas, chat y controles de viaje más confiables.
One complete release containing the selected KiloDrive mobile improvements through build 109.
KiloDrive 1.0.0+109 consolidates the reviewed release details from builds 92, 93, 94, 95, 96, 97, 101, 102, 105, 107 and 108. Their original summaries, descriptions and structured improvement cards are retained below, while the superseded build-log records are removed.
What this means for you: One complete release containing the selected KiloDrive mobile improvements through build 109.
Administration et inscription Apple plus fiables.
Les administrateurs système peuvent charger plus fiablement les tarifs, les offres d’adhésion et les informations des chauffeurs ou passagers. L’inscription Apple conserve le nom fourni lors de la première autorisation, demande en toute sécurité les informations manquantes et empêche la création de profils incomplets sans nom.
What this means for you: Administration et inscription Apple plus fiables.
More reliable administration and Apple registration.
System administrators can load fare settings, membership plans, and driver or rider details more reliably. Apple registration now carries the name supplied during first authorization, safely requests any missing name, and prevents incomplete blank-name profiles.
What this means for you: More reliable administration and Apple registration.
Administración y registro con Apple más confiables.
Los administradores del sistema pueden cargar con mayor fiabilidad las tarifas, los planes de membresía y los detalles de conductores o pasajeros. El registro con Apple conserva el nombre proporcionado durante la primera autorización, solicita de forma segura cualquier nombre faltante y evita perfiles incompletos sin nombre.
What this means for you: Administración y registro con Apple más confiables.
More reliable calling and stronger Android device validation.
Build 108 prevents duplicate outgoing call starts, preserves unknown call outcomes for safe reconciliation, binds media tokens to an active participant call session, and retains compatibility with build 106. Android release safeguards prevent test-only Firebase settings from entering release artifacts. Physical-device, two-client calling and background-location evidence is collected separately and is not implied by this changelog.
What this means for you: More reliable calling and stronger Android device validation.
More reliable scheduled work and safer Android release validation.
Build 107 fixes scheduled-report outbox transactions for MySQL retry strategies by keeping tenant locking, occurrence checks, outbox insertion and commit inside one execution-strategy unit. It preserves caller-owned transaction boundaries and keeps scheduled work idempotent after retries. Android packaged permission and service checks pass for location-only foreground tracking and protected in-app calling. This record does not claim iOS artifact availability, Google Play approval, or external provider certification.
What this means for you: More reliable scheduled work and safer Android release validation.
Clearer location-sharing controls and safer in-app calling.
Android accepted-trip GPS continues with a visible notification while the app is minimized or the screen is off, within the scoped session lifetime. Stop sharing and explicit Resume controls make that choice visible. Driver queue joins explain location use before permission and stop on leave or session expiry. In-app calls retain audio, mute, speaker and end controls, and end when the call screen or app is hidden or the device is locked. This Android candidate contains the runtime fixes absent from build 104; physical-device evidence and Play Console declaration reconciliation remain required. No iOS artifact or Google Play approval is claimed.
What this means for you: Clearer location-sharing controls and safer in-app calling.
Clearer role-specific trips, stronger ride recovery and safer financial reconciliation.
Trip guidance now speaks to the person using the screen, selected ride locations and fare inputs survive more lifecycle interruptions, and compact layouts keep important actions reachable. Provider-clearing reconciliation uses consistent snapshots and audited compensating evidence rather than changing immutable journal history. The release also expands deterministic two-client and native-provider verification tooling. Native store, real push, iOS and complete tap-driven journey certification remain separately evidenced and are not implied by this source release.
What this means for you: Clearer role-specific trips, stronger ride recovery and safer financial reconciliation.
Clearer trips, more dependable chat recovery and easier-to-use calculators.
Assigned drivers open the active trip automatically. Rapid chat sends retain their original identity during recovery, and chat dispatch is isolated from slow notification providers. Trip contact and safety actions use compact accessible layouts, notification sounds are bounded, and calculator result sheets keep Close reachable with large text or the keyboard open. Explicit social sign-in cancellation is handled as an expected outcome while genuine failures remain reportable. Features remain subject to country, account and provider availability; this release does not claim completed native-store or physical-device certification.
What this means for you: Clearer trips, more dependable chat recovery and easier-to-use calculators.
More dependable rentals, account verification and interrupted-payment recovery.
Rental bookings now preserve accepted provider-declared insurance or waiver terms, identify unavailable or expired information without blocking unrelated vehicle discovery, and keep temporary inventory and payment holds clear. Account verification and security challenges handle concurrent use more safely, while retryable money and membership actions retain their original operation identity after interrupted responses. Availability remains governed by country policy, deployed API configuration and provider readiness; KiloDrive does not provide rental insurance.
What this means for you: More dependable rentals, account verification and interrupted-payment recovery.
Clearer driver work, safer account recovery and more dependable wallet actions.
Driver Work now explains readiness blockers and keeps offer actions readable while moving. Account, contact and social sign-in recovery paths provide specific next steps, while wallet and membership actions preserve state after interrupted requests and show clear confirmation. Ride, onboarding, safety and billing screens retain last-good data during refresh failures and keep sensitive actions behind current authorization. Availability remains governed by country policy and the matching deployed API; this release does not claim external provider certification.
What this means for you: Clearer driver work, safer account recovery and more dependable wallet actions.
Compare membership plans more easily, finish account setup and manage wallet activity with clearer feedback.
Compare plans, benefits and exact store prices under one duration slider in Billing and the final driver setup page. Verify email and phone on separate onboarding pages. Driver welcome email is sent after setup is complete. Scan a top-up card QR code, review its code before redeeming and see the confirmed credit or a clear already-redeemed message. Sort transactions by date or amount and filter wallet credits and debits. Cancelled native checkout recovers without leaving the next purchase stuck pending. Availability depends on country policy, the matching deployed API and store configuration; this release does not claim completed provider sandbox certification.
What this means for you: Compare membership plans more easily, finish account setup and manage wallet activity with clearer feedback.
A clearer Driver Work space and a smoother start with social sign-in.
Driver Work now separates offers, actions needed and driver settings into accessible tabs. Location guidance can be dismissed when location is ready, while important location warnings remain visible. When a verified social account is not linked to KiloDrive, sign-in offers a clear choice to create a free account without creating one automatically. Subscription recovery better handles cancellation and verified entitlement changes. Country and provider availability still apply; this release does not claim completed Apple or Google sandbox certification.
What this means for you: A clearer Driver Work space and a smoother start with social sign-in.
Aligned driver memberships with the reviewed Apple subscription catalogue.
Build 92 uses the exact reviewed Apple product identifiers for Silver and Gold weekly, monthly and quarterly subscriptions, while keeping core membership information available if the native store is temporarily unavailable.
What this means for you: Aligned driver memberships with the reviewed Apple subscription catalogue.
A clearer Security Center, unified financial history, and more reliable sign-out.
Manage authentication, connected accounts, passkeys and sessions in one Security Center. Billing & Financial brings membership, wallet activity and transaction history together. Session recovery is more resilient to interrupted requests, and account changes clear private screens and cached account data without allowing a late response to restore an old session. Availability still depends on country policy and the deployed API; this release does not claim certification of external payment providers.
What this means for you: A clearer Security Center, unified financial history, and more reliable sign-out.
One complete release covering safer accounts, dependable onboarding, clearer billing, stronger privacy, reliable trips and mature marketplace operations.
KiloDrive 1.0.0+89 brings the reviewed improvements from the selected earlier mobile releases into one complete release record. It combines safer registration and social sign-in, authoritative driver onboarding, clearer store membership behavior, stronger trip and wallet recovery, improved privacy and safety controls, more dependable rentals and administration, and broader release-quality safeguards. The detailed improvement cards below retain the full reviewed history and explain the benefit of each change.
What this means for you: One complete release covering safer accounts, dependable onboarding, clearer billing, stronger privacy, reliable trips and mature marketplace operations.
More reliable typed workspaces and safer recovery across the app.
KiloDrive 1.0.0+88 completes the next migration of lower-frequency administration and operational screens to typed repositories, improves last-good-data recovery during refreshes, and strengthens release-time contract checks so mobile, API and Portal behavior stay aligned.
What this means for you: More reliable typed workspaces and safer recovery across the app.
More reliable account entry and store-ready membership recovery.
KiloDrive 1.0.0+86 improves account creation and social sign-in feedback, keeps signup country selection explicit, and tightens store membership contract validation so unavailable products fail safely without hiding the current plan.
What this means for you: More reliable account entry and store-ready membership recovery.
Safer purchases, smoother Apple sign-in, and more dependable trip and wallet recovery.
KiloDrive 1.0.0+84 improves Apple membership purchases and account creation, strengthens retry-safe trip, wallet and administration actions, and makes important rider, driver, rental and support screens recover more predictably from stale data, interrupted responses and application restarts.
What this means for you: Safer purchases, smoother Apple sign-in, and more dependable trip and wallet recovery.
More dependable rentals, communication readiness, and release recovery.
KiloDrive 1.0.0+83 strengthens rental authorization, idempotent retry and checkout state handling, makes provider configuration fail safely when required voice resources are invalid, and improves release validation across account setup, delivery, administration, and marketplace workflows.
What this means for you: More dependable rentals, communication readiness, and release recovery.
Safer trips, clearer onboarding, and more reliable marketplace workflows.
KiloDrive 1.0.0+82 strengthens active-trip safety and recovery, makes signup and onboarding easier to resume, and improves the clarity and reliability of ride, account, support, and marketplace workflows. This release also gives operations teams more structured states and evidence without exposing technical payloads to end users.
What this means for you: Safer trips, clearer onboarding, and more reliable marketplace workflows.
Refined mobile experiences with updated user guidance.
Build 81 paired mobile refinements with refreshed manuals so product behavior and user guidance remained aligned.
What this means for you: Refined mobile experiences with updated user guidance.
Matured platform workflows and production readiness.
Build 80 consolidated reviewed workflow improvements and production-readiness work into one mobile milestone.
What this means for you: Matured platform workflows and production readiness.
A refreshed mobile package with an updated build identity.
Build 79 advanced the application package identity so it could be distributed and reviewed independently.
What this means for you: A refreshed mobile package with an updated build identity.
Hardened onboarding notifications and administration.
This release improved driver onboarding notifications and the operational tools used to manage their outcomes.
What this means for you: Hardened onboarding notifications and administration.
Improved App Store compliance and platform certification.
Build 75 aligned mobile behavior and disclosures with reviewed App Store requirements and platform workflow evidence.
What this means for you: Improved App Store compliance and platform certification.
Hardened release-build privacy and symbol handling.
Build 70 strengthened the release pipeline around AOT privacy checks and production packaging.
What this means for you: Hardened release-build privacy and symbol handling.
Expanded marketplace safety and operational tools.
This release milestone brought additional safety and marketplace-operational capabilities into the mobile experience.
What this means for you: Expanded marketplace safety and operational tools.
Deployed broader marketplace updates.
Build 69 packaged reviewed marketplace changes for the next production release.
What this means for you: Deployed broader marketplace updates.
Control active-trip location sharing
Notification Stop and explicit trip Resume controls preserve the choice to stop sharing; scoped expiry and stale-session guards bound collection.
What this means for you: Keep journey GPS available when needed and clearly stop or resume sharing.
Understand queue location use
A queue-specific explanation precedes permission and joining. Leaving stops local tracking, and expired or terminal sessions cannot continue collecting indefinitely.
What this means for you: Know why queue location is used and when it stops.
Safer foreground in-app calls
Pending connections and microphone actions cannot reactivate an ended call. Leaving the call screen or app, or locking the screen, ends the call without stopping independent trip GPS.
What this means for you: Use audio, mute, speaker and end controls with clear microphone lifetime.
Stronger Android release checks
Native lifetime tests and packaged APK/AAB manifest checks enforce the location-only foreground-service boundary.
What this means for you: Receive a release checked against its declared permission boundary.
Role-correct trip guidance
Trip status explanations now distinguish Driver and Rider audiences while preserving the stable API status contract.
What this means for you: Drivers no longer see wording that refers to themselves as the rider's driver, and both roles receive clearer next steps.
More resilient ride creation
Recent-location selection, fare inputs and the request action remain coherent through transient map, keyboard and restoration changes.
What this means for you: Riders can complete a request with fewer obstructed controls and less lost input.
Safer provider-clearing reconciliation
Clearing checks use one consistent snapshot and audited compensating postings while preserving immutable journals.
What this means for you: Financial discrepancies are easier to explain and repair without rewriting transaction history.
Expanded release evidence
Two-client, guest-restoration and native-provider harnesses now retain clearer sanitized evidence and distinguish implementation from external certification.
What this means for you: Support and release teams can make safer release decisions from evidence tied to the actual build.
Open the assigned trip automatically
Acceptance and resume reconcile the current assignment without duplicate navigation or crossing account and country workspaces.
What this means for you: Reach the next trip action with fewer taps.
More dependable rapid-message recovery
Queued sends keep stable identities and chat dispatch has its own bounded outbox lane; replaced worker claims cannot overwrite newer state.
What this means for you: Recover conversations more reliably when connectivity or notification providers are slow.
Keep calculator Close within reach
Pinned Close, keyboard and Escape dismissal, accessible semantics and wrapping result rows improve long result sheets without changing formulas.
What this means for you: Read results and return to another calculator more easily on small screens or with large text.
Clearer trip actions and cancellation diagnostics
Trip contact and safety actions are grouped, notification sounds are bounded, and explicit social-login cancellation is separated from actual provider failures.
What this means for you: Spend less time dealing with repeated alerts or confusing interruption states.
Clear provider-managed insurance information
Rental booking details distinguish provider-declared insurance or waiver terms from KiloDrive services and show explicit unavailable, not offered, expired and period-not-covered states.
What this means for you: Understand who provides the terms and whether they apply to the selected rental dates.
Safer rental holds and eligibility checks
Temporary inventory holds, provider authorization deadlines and country-aware driver and vehicle eligibility are revalidated at important booking transitions.
What this means for you: Receive clearer next steps when a hold, document or provider authorization needs attention.
Stronger one-time challenge handling
Verification and step-up challenges use bounded, single-use outcomes under concurrent requests and keep private codes out of diagnostics.
What this means for you: Complete sensitive account actions with more reliable verification feedback.
Recovery after interrupted actions
Retryable payment and account operations preserve their original request identity and refresh only affected information after recovery.
What this means for you: Avoid duplicate actions and see an accurate result after a slow or interrupted connection.
A clearer Driver Work dashboard
Readiness, active vehicle, compliance, membership, location freshness, online lease, assignment and earnings are presented as independent cards with one next action for each blocker.
What this means for you: Know exactly what needs attention before accepting work.
More reliable sign-in and account recovery
Social sign-in collisions, contact verification and session recovery now provide explicit, localized outcomes without losing the pending action.
What this means for you: Recover access without guessing what to do next.
Retry-safe money actions
Wallet and membership mutations preserve their idempotency context, distinguish pending from failed outcomes and refresh only the affected balances and history.
What this means for you: See an accurate result after a slow connection or interrupted checkout.
Safer refresh and recovery states
Critical ride, onboarding, safety and billing screens retain last-good information, identify stale data and disable actions whose authorization or preconditions cannot be revalidated.
What this means for you: Stay informed during service interruptions without acting on stale information.
Compare plans in one place
One duration slider updates bold native-store prices across responsive plan cards, with benefits, review and restore actions.
What this means for you: Understand the selected term, price and benefits before deciding.
Clearer contact verification and final membership choice
Email and phone have separate verification pages. Membership comparison is the final step, and driver welcome mail waits for completed setup.
What this means for you: See the next verification action and finish setup without premature welcome messages.
Clear top-up card results and QR scanning
Scan a ten-digit card QR code for review, redeem explicitly and see the confirmed value or a localized invalid/already-redeemed message.
What this means for you: Enter card codes more easily and understand whether credit was applied.
More useful transaction history and checkout recovery
Sort history by date or amount, filter wallet credits and debits, prevent self-recipient additions and recover after cancelling native checkout.
What this means for you: Find money movements faster and retry an intentionally cancelled purchase.
Apple subscription catalogue alignment
Build 92 uses the exact reviewed Apple product identifiers for Silver and Gold weekly, monthly and quarterly subscriptions, while keeping core membership information available if the native store is temporarily unavailable.
What this means for you: Drivers can select a reviewed membership term and receive clearer, recoverable billing behavior during App Store availability issues.
A dedicated Security Center
Use swipeable sections for authentication, sessions, passkeys, connected social accounts and security settings, with guided two-factor setup.
What this means for you: Find account protection controls in one place.
Safer session recovery
Refresh requests share one recovery operation. Late responses from an old account are discarded, and an authoritative revoked-session response clears account-bound state and private navigation.
What this means for you: Avoid repeated login errors and stale private screens when a session expires or an account changes.
One financial workspace
Membership, transfers, top-ups, cashouts, reports and typed transaction history share the Billing & Financial workspace. Membership updates refresh affected account data.
What this means for you: Review money activity and current membership without switching between disconnected screens.
Typed operational screens
Administrative and operational workspaces now keep typed state, preserve successful data during refresh errors, and report safe retry guidance instead of exposing transport details.
What this means for you: The app stays useful during intermittent connectivity and gives a clear next action when only one card or data source is unavailable.
Coherent registration intent
Country, role, contact method and organization choice now travel through first run, registration, social authentication and recovery as one reviewed intent. Active-country validation runs on both client and API boundaries.
What this means for you: People can resume signup without repeating choices or accidentally creating the wrong account type.
Verified social and contact boundaries
Social email is accepted only with a verified provider claim, automatic email-only account linking remains prohibited, and onboarding contact mutations require fresh action-bound confirmation before email or phone verification.
What this means for you: Account ownership changes are harder to misuse while legitimate social and contact verification remains understandable.
Authoritative driver readiness journey
Identity, membership, contacts, preferences, vehicle evidence, optional rating import, business settings and legal consent are evaluated by the API from current evidence and persisted revisions. Evidence overrides cannot waive driver-owned legal acceptance.
What this means for you: Drivers return to the correct step and cannot be marked ready while an important setup or legal requirement is incomplete.
Safer interrupted-operation recovery
Registration projection, onboarding revisions, idempotent retries and post-commit audit handling now distinguish incomplete work from a completed operation whose diagnostic follow-up was temporarily unavailable.
What this means for you: Temporary connectivity or diagnostic failures are less likely to create duplicate accounts, repeated submissions or misleading error messages.
More dependable App Store membership purchases
Apple storefront prices, signed transactions, restore events and interrupted verification attempts now follow one exact, retry-safe purchase contract.
What this means for you: Membership purchases and restores are clearer and less likely to fail or duplicate after a temporary connection problem.
Smoother Sign in with Apple
KiloDrive now uses the name and private relay email supplied by Apple, supports returning authorization without another registration form, and provides secure recovery when an Apple identity is already connected.
What this means for you: Apple users can create or reopen their KiloDrive account with fewer repeated questions and clearer recovery guidance.
Retry-safe trip and wallet actions
Important ride, bid, trip, chat, payment and wallet changes retain stable operation identity and current server revisions across timeouts, refreshes and application restarts.
What this means for you: Repeated taps and uncertain network responses are less likely to create duplicate actions or stale screens.
Stronger release and screen-state checks
The release now includes broader contract, localization, responsive layout, state recovery, schema and production configuration safeguards.
What this means for you: Users receive more consistent loading, error and recovery behavior across rider, driver, rental and administration workflows.
Clearer signup and social sign-in recovery
Signup country selection is explicit, social actions have bounded recovery, and provider-specific failures explain the next safe step.
What this means for you: People can finish account setup without a silent spinner or an ambiguous registration state.
Exact cross-store membership mapping
Apple product identifiers, Google product identifiers and plan terms are checked independently before purchase controls are enabled.
What this means for you: A membership purchase is offered only when the selected plan, term and store product are genuinely available.
More reliable rental actions
Rental permissions are checked before mutation work, uncertain network outcomes preserve their idempotency key, and booking payment transitions use stricter concurrency and state checks.
What this means for you: Rental actions recover more predictably from repeated taps, interrupted responses, and competing updates.
Safer communications configuration
AWS Voice readiness now requires the provider resource identifier expected by the service and fails closed when that boundary is invalid.
What this means for you: Invalid voice configuration is detected before it can masquerade as a working verification channel.
Stronger release certification
The authenticated fixture coordinator, cleanup guard, evidence-privacy scan, localization policy, and loading-state classifications now agree on one reproducible release boundary.
What this means for you: Users receive a package that passed broader automated checks before it was prepared for distribution.
Safer, more resilient active trips
Active-trip location, trip-state recovery, location freshness, and telemetry-gap handling now work together around explicit trip lifecycle states.
What this means for you: Riders and drivers receive clearer live-trip status and less uncertainty when the app, network, or realtime connection is interrupted.
Clearer signup and onboarding
Registration intent and incomplete onboarding journeys are restored consistently, while the driver journey presents identity, contact, vehicle, document, preference, and legal steps in one resumable flow.
What this means for you: People can continue where they left off and understand the next required action without repeating their country or account choices.
More mature marketplace and account tools
Ride negotiation, multi-stop, hourly and scheduled workflows now present clearer states alongside typed membership, support, audit, and account-management experiences.
What this means for you: Users get clearer choices and feedback while completing trips or managing their KiloDrive account.
Production workflow maturity
Build 80 consolidated reviewed workflow improvements and production-readiness work into one mobile milestone.
What this means for you: Users receive more predictable behavior across connected KiloDrive services.
Mobile guidance alignment
Build 81 paired mobile refinements with refreshed manuals so product behavior and user guidance remained aligned.
What this means for you: People can understand new and changed behavior through clearer in-app experiences and supporting guidance.
Onboarding communication
This release improved driver onboarding notifications and the operational tools used to manage their outcomes.
What this means for you: Drivers and administrators receive clearer confirmation and follow-up during setup.
Release identity refresh
Build 79 advanced the application package identity so it could be distributed and reviewed independently.
What this means for you: Store reviewers and support teams can distinguish this package from earlier builds.
Store compliance maturity
Build 75 aligned mobile behavior and disclosures with reviewed App Store requirements and platform workflow evidence.
What this means for you: Users receive clearer platform-appropriate disclosures and review-ready behavior.
Marketplace safety operations
This release milestone brought additional safety and marketplace-operational capabilities into the mobile experience.
What this means for you: Riders, drivers and operations teams receive clearer safety and workflow signals.
Marketplace update
Build 69 packaged reviewed marketplace changes for the next production release.
What this means for you: Ride and service workflows feel more consistent across the platform.
Release privacy hardening
Build 70 strengthened the release pipeline around AOT privacy checks and production packaging.
What this means for you: Production packages expose less unnecessary implementation detail while remaining supportable through retained private symbols.
Country-aware workflow maturity
Build 66 advanced country-aware operation while refining the everyday rider, driver and administrative workflows.
What this means for you: People receive behavior that better reflects the country workspace they are using.
Production alignment
Build 63 was prepared with the corresponding API and schema alignment work.
What this means for you: The installed app and production services share a more consistent contract.
Contract hardening
This release strengthened the executable contract between the app and API and packaged the result as build 64.
What this means for you: Unexpected service responses are handled more predictably.
Onboarding and billing clarity
Driver onboarding and billing workflows were matured while Android packaging was aligned with the reviewed platform policy.
What this means for you: Drivers get clearer setup and membership interactions in a policy-aligned Android build.
Security and workflow hardening
Build 61 consolidated security-boundary, workflow and platform hardening into a release package.
What this means for you: Users benefit from stronger account protection and more dependable workflows.
Platform synchronization
This milestone brought coordinated mobile, API and operational changes into a consistent platform update.
What this means for you: Features behave more consistently across the app and supporting services.
Administration workflow maturity
Android build 59 included clearer administration workflows and a refreshed release package.
What this means for you: Authorized administrators can complete operational tasks with clearer context and actions.
Lower membership pricing
The active membership catalogue was revised to the reviewed fifty-percent-reduced pricing model.
What this means for you: Eligible drivers can access paid membership benefits at the reduced reviewed price.
Production contract refresh
Build 51 was prepared after schema alignment so the application and API contract remained synchronized.
What this means for you: Users encounter fewer client/server mismatches after upgrading.
Mobile release package
Mobile build 52 consolidated the reviewed application changes into a distinct release package.
What this means for you: Users and support teams can identify the updated application reliably.
Cross-platform build identity
The Android and iOS build identities advanced together for a consistent cross-platform release milestone.
What this means for you: Store and support teams can identify equivalent Android and iOS packages more easily.
Android release identity
This milestone advanced the Android build identity for distribution and review.
What this means for you: The corrected Android package can be distinguished cleanly from prior submissions.
Mobile state maturity
Build 39 refined how mobile screens preserve and present state during normal loading and interaction changes.
What this means for you: Screens behave more predictably while information is loading or being refreshed.
Release and schema alignment
This release milestone paired build 40 with the reviewed production schema contract.
What this means for you: Users receive a client package designed for the same contract running in production.
Toll tools
Build 42 packaged the reviewed toll-tool experience for release.
What this means for you: Drivers and riders can make better-informed travel-cost decisions.
Toll catalogue alignment
The toll catalogue and mobile presentation were aligned so route-cost tools use the same reviewed reference information.
What this means for you: Displayed toll information is more consistent with the supporting reference catalogue.
Bidding and setup progress
The marketplace expanded bidding visibility while account setup gained more explicit progress guidance.
What this means for you: Drivers can discover more eligible opportunities and new users can better understand what remains to finish setup.
Lifecycle recovery
Application lifecycle behavior and operational integration were hardened so interrupted or resumed sessions behave more consistently.
What this means for you: Users are less likely to lose context when the app backgrounds, resumes or reconnects.
Unified build numbering
Android and iOS packaging identifiers were brought under one reviewed numbering approach, with matching manual release references.
What this means for you: Support and store reviewers can identify the exact KiloDrive package more reliably.
Schema-aligned package
Build 37 was prepared against the reviewed database schema so the client and production contract could move forward together.
What this means for you: The app is less likely to encounter contract mismatches after deployment.
Calculator alignment
The KiloDrive calculator experience was aligned and packaged with mobile build 38.
What this means for you: People receive more consistent calculation tools inside the app.
Ride communication and reviews
Notifications, ride interactions and post-trip review behavior were matured together in this release milestone.
What this means for you: Riders and drivers receive clearer trip updates and a more complete post-trip feedback flow.
Platform hardening
Build 23 consolidated security, contract and operational hardening into a reviewed mobile release milestone.
What this means for you: Users benefit from a more dependable app while sensitive operations receive stronger safeguards.
Identity workflow hardening
Identity operations were refined and packaged into build 24 with clearer handling around account-sensitive workflows.
What this means for you: Account setup and security actions are more predictable and easier to recover.
Ride dispatch experience
Ride dispatch and the passenger trip experience were matured together so requesting, matching and following a ride use more coherent states.
What this means for you: Riders receive clearer feedback while a request moves toward an assigned trip.
Currency and schema alignment
Build 13 aligned currency behavior with the supporting schema contract so money presentation and persisted values remain consistent.
What this means for you: Prices and financial records are less likely to disagree across the app and service.
Membership accounting maturity
Membership behavior and its accounting treatment were matured together, keeping product access and financial records closer to the same source of truth.
What this means for you: Drivers receive clearer membership outcomes while operations retain more dependable financial evidence.
Receipts and store workflow
This milestone combined mobile workflow refinements with clearer receipts and store packaging work.
What this means for you: Users get clearer proof of completed financial actions and a more polished release experience.
Store membership support
The mobile membership experience was aligned with store purchase requirements so plans could be represented through reviewed store products.
What this means for you: Drivers can understand membership choices through a store-compatible purchase experience.
Provider membership refinement
This release finalized commission-free provider membership behavior and clarified how membership supports driver access.
What this means for you: Drivers receive a more predictable relationship between their plan and marketplace access.
Membership contract alignment
Membership workflows were certified against the corresponding schema contract before this mobile build was prepared.
What this means for you: Membership status is less likely to drift between the app, API and database.
iOS location disclosure
The iOS deployment target and location disclosure were aligned so supported devices receive accurate privacy context before location-dependent features are used.
What this means for you: People receive clearer information about why KiloDrive needs location access on supported iPhones and iPads.
iOS release identity
This packaging milestone advanced the iOS build identity so the corrected application could be distributed and reviewed as a distinct build.
What this means for you: Store delivery and support teams can distinguish this corrected package from earlier builds.
Release package preparation
This documented build prepared the application package and release identity for subsequent rider, driver and operational improvements.
What this means for you: Users receive an identifiable, supportable application package rather than an ambiguous rebuild.
Platform workflow maturation
This release milestone consolidated platform workflow improvements into mobile build 11 and prepared them for distribution.
What this means for you: Common tasks feel more coherent and are easier to support across the KiloDrive experience.
Modern mobile foundation
This first documented mobile milestone brought the modern KiloDrive application foundation together with the release and publishing assets needed to present it consistently.
What this means for you: A clearer, more consistent base experience made later rider, driver and administration improvements possible.