How MI Spekter Gave EV Charging Engineers a Diagnostics App That Works Offline
MI Spekter's charging station testers needed a companion app that worked without internet. easy.bi built an offline-capable Angular browser app with workspace reporting and cross-device compatibility.
The Challenge: Field Engineers With No Reliable Internet
MI Spekter manufactures electronic testing devices, including the Charging Station Tester (CST) - a specialized device that analyzes and verifies electrical charging stations for electric vehicles. As the EV charging network expands across Europe, demand for testing and certification has grown rapidly.
Field engineers use the CST to diagnose charging stations at installation sites, parking structures, highway rest stops, and urban charging hubs. The problem: many of these locations have limited or no internet connectivity. Underground parking garages, rural highway stations, and construction sites are dead zones for mobile data.
Without a reliable digital companion app, engineers relied on manual note-taking and paper reports. Test results were recorded by hand, transported back to the office, and then entered into digital systems. This process was slow, error-prone, and made it impossible to share findings with colleagues in real time.
MI Spekter needed a browser-based application that worked fully offline, ran on any device an engineer might carry - laptop, tablet, or phone - and provided structured workspaces for organizing test data, generating reports, and collaborating with team members once connectivity returned.
“Half the charging stations we test are in underground garages or remote highway stops. If the app needs internet, it's useless where we actually work.”
Why MI Spekter Chose easy.bi
Building offline-capable browser applications requires specific technical expertise. Most web apps assume persistent connectivity - handling offline mode as an edge case rather than a primary requirement. MI Spekter needed a team that would design offline-first from the ground up.
easy.bi had experience building progressive web applications with Angular's service worker capabilities and offline data synchronization patterns. The team understood both the technical requirements (local storage, sync queues, conflict resolution) and the practical realities of field engineering workflows.
“easy.bi understood that offline wasn't a 'nice-to-have' - it was the core requirement. They built the entire architecture around it instead of treating it as an afterthought.”
The Approach: Offline-First, Field-Ready
Offline-first architecture. easy.bi designed the application with offline capability as the primary mode, not an afterthought. All core functionality - station selection, test execution, data entry, and report generation - works without an internet connection. Data is stored locally and synchronized to the server when connectivity becomes available.
Workspace-based organization. The app organizes test data into workspaces. Each workspace contains all relevant information about a charging station - location, test parameters, results, and notes. Engineers can manage multiple workspaces simultaneously, switching between stations without losing context. This structure mirrors how field engineers actually work: moving between sites throughout the day.
Report generation and sharing. Within each workspace, engineers generate structured reports directly from test data. Reports follow a standardized format for certification documentation. Once online, reports can be shared with colleagues, exported for client delivery, or printed for on-site documentation.
Cross-device compatibility. The application was built as a browser-based app using Angular, ensuring it runs on any device with a modern browser. Engineers use whatever hardware they have - laptops for detailed analysis, tablets for on-site work, phones for quick checks. The UI adapts to each screen size without losing functionality.
Angular implementation. Angular was chosen for its service worker support, component architecture, and ability to handle complex state management in offline scenarios. The framework's built-in tools for progressive web app functionality aligned directly with MI Spekter's requirements.
“We used to write test results on paper and type them in at the office. Now everything goes straight into the app on-site. The time savings are significant, and the error rate dropped to nearly zero.”
The Results: Structured Diagnostics, Anywhere
The diagnostics app eliminated the paper-based workflow entirely. Field engineers now capture test results digitally at the point of testing - whether they have internet or not. Data entry errors dropped because results go directly from the testing device into structured workspaces rather than being transcribed from handwritten notes.
Collaboration improved significantly. Engineers who previously worked in isolation now share workspaces and reports with colleagues once they reconnect. Problem identification is faster because multiple engineers can review the same test data and add their observations.
The cross-device compatibility proved particularly valuable. Engineers use tablets during physical testing, switch to laptops for detailed analysis and report writing, and check workspace summaries on their phones between sites. The app works the same way on every device.
“The workspace model matches how we actually work. I test five stations in a day, and each one has its own workspace with all the data organized. At the end of the day, I sync and share. It's simple.”
Key Takeaways
- Offline-first requires a fundamentally different architecture. Bolting offline support onto a connected app creates a poor experience. Designing for offline as the primary mode ensures the app works everywhere - and connectivity becomes a bonus, not a requirement.
- Match the app structure to the workflow. The workspace model succeeded because it mirrors how field engineers already organize their work - by station, by site, by day. Technology should adapt to the user, not the other way around.
- Cross-device support expands utility beyond the original use case. Engineers discovered uses for the app that weren't in the original spec - precisely because it worked on every device they carried.
- Browser-based apps reduce deployment friction. No app store submissions, no device-specific builds, no installation requirements. Engineers open a URL and start working.
Ready to achieve similar results?
Speak directly with our experts. Book a 20-minute Expert Call.
Start with a Strategy CallProject Snapshot
More success stories
Multi-brand e-commerce platform with SSO for outdoor brands
Order processing middleware for multi-store Shopify operations
