Stabilising and Evolving a Connected Mobility Platform at Scale

Delivered by Infarsight in collaboration with a specialist mobility partner

Client Context

The client operates a large-scale connected mobility platform where mobile applications act as the primary interface between users, vehicles, and backend systems.

The platform supports:

• Real-time vehicle interactions
• Continuous user journeys
• Device and Bluetooth-based connectivity
• High-volume, customer-visible operations

The mobile application was not a companion experience , it was a core operational surface. Any instability surfaced immediately to users and escalated rapidly within the organisation.

Infarsight was engaged alongside a specialist mobility partner to bring architectural judgment, stabilisation discipline, and system-level coordination to the programme.

The Challenge

This was not a greenfield build.

The platform was already live and operating at scale, with:

• Active users and production traffic
• Deep coupling between mobile apps, vehicle systems, and backend services
• Variable connectivity across geographies and journeys
• High escalation sensitivity at leadership levels

Key challenges included:

1. Mobile as the Visible Failure Surface

Although issues originated across devices, networks, and backend systems, failures consistently surfaced in the mobile app, creating the perception that mobile engineering was the primary problem.

2. Connectivity and State Volatility

Bluetooth connectivity, intermittent networks, and delayed telemetry led to:

• State mismatches between vehicle, app, and backend
• Inconsistent user experiences during transitions
• Unpredictable behaviour under degraded conditions

3. Live Platform Evolution

The platform required architectural evolution and stabilisation without disrupting business-as-usual operations. There was no appetite for rewrites, downtime, or high-risk change.

Infarsight’s Role

Infarsight was brought in to act as a system-level engineering partner, working in close collaboration with a specialist mobility implementation partner.

Our responsibility focused on:

• System behaviour and reliability
• Mobile engineering judgment beyond UI and feature delivery
• Safe evolution of a live, connected platform

This was not a takeover engagement — it was a co-execution model with clear boundaries and shared accountability.

Approach

1. Reframing Mobile as a System Boundary

Rather than treating mobile as a presentation layer, the platform was reframed with mobile as:

• A convergence point for users, vehicles, connectivity, and backend services
• A reflection of system-level coordination quality
• A surface where volatility must be absorbed predictably

This reframing shifted the focus from UI fixes to state, timing, and dependency coordination.

2. Stabilisation Before Acceleration

The initial phase prioritised:

• Observing real production behaviour
• Identifying failure modes under degraded connectivity
• Understanding Bluetooth and device state transitions
• Reducing escalation triggers before introducing change

This stabilisation-first posture ensured operational calm while deeper issues were addressed.

3. State-Driven Mobile Engineering

Key engineering interventions focused on:

• Reliable state synchronisation between device, app, and backend
• Explicit handling of offline, online, and degraded modes
• Gating user actions based on system readiness, not UI flow
• Improving background execution and lifecycle handling to reduce battery drain

These changes reduced unpredictability without altering core user journeys.

4. Incremental Evolution Without Disruption

Instead of large-scale rewrites:

• Improvements were introduced incrementally
• Changes were scoped to minimise blast radius
• Existing teams and vendors continued BAU operations
• Ownership and responsibility evolved gradually

This allowed architectural improvements to land without destabilising live operations.

Outcomes

The engagement delivered measurable, operationally meaningful outcomes:

• Improved mobile stability under volatile connectivity conditions
• Reduced escalation frequency, particularly for Bluetooth and state-related issues
• Predictable mobile behaviour across journeys and transitions
• Preserved BAU continuity during platform evolution
• Increased confidence among stakeholders in the platform’s ability to evolve safely

Most importantly, the organisation moved from reactive firefighting to controlled, system-level decision-making.

Infarsight’s Contribution

Infarsight acted as an architectural and engineering steward, ensuring that:

• Stability was protected first
• Change was introduced deliberately
• Existing teams retained ownership
• Decisions were informed by patterns, not assumptions

Delivered in partnership. Owned for outcomes

Why This Matters to Enterprise Leadership

For leadership teams, the biggest risk in connected mobility platforms is not feature gaps — it is loss of control.

This engagement restored predictability across a live platform, reduced escalation noise, and enabled architectural change without triggering operational instability.

The result was not just a more stable application, but renewed confidence that the platform could evolve safely.

Recurring Pattern Observed

Across connected mobility platforms, instability rarely originates in the mobile UI. It emerges from how state, connectivity, and dependencies are coordinated under real-world conditions.

Treating mobile as a system boundary — not a presentation layer — is what enables reliability at scale