What's Coming Next
Version 1.1.0 is a substantial step. The natural question is: what comes next? Here is the rough shape of where MileClear is heading, organised by when each piece is realistic.
None of this is a hard commitment. Solo development moves with the data, and the data sometimes says "do this thing instead". But the direction is set.
Coming in 1.2 (next few weeks)
Community pickup-wait insights
The pickup wait timer in 1.1.0 collects per-driver data. The aggregation surface is what makes that data valuable: "this McDonald's averages 12-minute waits across 8 drivers", "Friday evenings here are 18 minutes". Once enough drivers are using the timer, the average wait at every pickup point becomes a useful piece of intelligence. Couriers will be able to avoid the consistently slow ones.
Privacy floor is the same as Anonymous Benchmarking - never show a bucket with fewer than 5 contributors.
Deeper Anonymous Benchmarking
1.1.0 ships national-level benchmarks. As the user base grows, regional breakdowns become statistically meaningful: "drivers in your postcode area average X miles per week". The infrastructure is ready; the data needs to catch up. Expect regional benchmarks to appear automatically for Greater London, Greater Manchester, Birmingham, Glasgow, and Edinburgh first, then expand outward as density increases.
Onboarding revamp
The biggest gap in MileClear's funnel today is users who classify trips but never log earnings. Without earnings, the tax estimate cannot work, and the user gets less than half the value of the app. The 1.1.0 earnings nudge addresses this for active users; the next step is rebuilding the first-launch experience so new users understand from day one why earnings logging matters.
HMRC reconciliation auto-fill
Right now you type in HMRC's reported figure manually. There is a Self Assessment Accounts API that, with the user's consent, would let MileClear fetch this directly. That requires HMRC production accreditation (multi-week process), so it is not 1.2 work but it is on the path.
Coming in 1.3 - 1.4 (next few months)
MTD ITSA quarterly submission
From April 2027, every self-employed person earning over £30,000 a year will be required to submit quarterly digital updates to HMRC. The threshold for April 2026 is £50,000, and a large slice of full-time gig drivers will be caught by April 2027.
The MileClear sandbox application is already registered with HMRC's Developer Hub, with all 9 relevant Self Assessment APIs subscribed. The work to come is the OAuth flow, the submission mechanics, the fraud-prevention headers HMRC requires on every call, and the production accreditation process. This is a multi-week project but it is the most strategically important feature for self-employed drivers approaching the MTD deadline.
The pitch is simple: drivers will need software that submits their quarterly figures to HMRC. If MileClear is the bridge, that is a defensive moat - competitors have to build the same thing or lose users.
Vehicle maintenance log
Service intervals, oil changes, tyres, brakes. Push reminders ahead of due dates. For owner-driver-franchisees running £30,000 Sprinters, missing a service is real money. Builds on the existing DVLA + DVSA integrations.
Insurance broker partnership
Most UK gig drivers are either underinsured or paying too much for the wrong policy class. A "Find Insurance" screen would let drivers compare quotes from regulated UK gig-insurance brokers (Zego, Inshur, etc.) with one tap. The compliance work is non-trivial - FCA rules about advice vs introduction matter here - but the value to drivers is clear.
Strategic plays (long-term)
Verified mileage handoff to insurers
None of the gig-economy insurers have built a verified-mileage product, even though pay-per-mile insurance literally needs that data. If MileClear becomes the trusted source-of-truth for "miles driven for work" that insurers consume via API, that is a B2B moat plus a co-marketing channel.
Native tracking module
The current tracking layer runs in JavaScript via Expo. iOS can suspend the JS runtime mid-trip, which is the root cause of several reliability bugs we have layered fixes against. The proper long-term solution is a Swift native module that runs outside the JS runtime. This is a serious investment - 4-8 weeks of focused work - and only justified once the user base is big enough that reliability variance becomes a churn problem. Not yet, but on the radar.
Android
iOS-only is fine for now: 80% of the gig-driver target audience uses iPhone. But Android coverage is the natural next platform once the iOS app is genuinely stable. Android is a deferred 1.x or 2.0 release.
Things that are not on the roadmap
Worth being explicit about a few things MileClear is not going to do, because being focused matters more than being feature-complete.
- Generic budgeting / savings goals. Banking apps do this better. MileClear is for drivers, not the general public.
- Multi-currency / international. UK-only. The whole product is built around HMRC, AMAP rates, and UK gig platforms. Going international would require redoing every assumption.
- Stocks, crypto, investments. Out of scope. MileClear is about earning more from driving, not about what to do with the savings.
- An Android-style fully customisable dashboard. The layout-customisation that already exists in 1.0.x is the limit. More flexibility just adds complexity without changing user outcomes.
How to influence what's next
The roadmap moves with the data. If you are using the app and something feels missing, tell me - either through the in-app feedback screen, the MileClear Facebook group, or directly to gair@mileclear.com.
I read every message. Several of the features in 1.1.0 came directly from things drivers said they wanted: vehicle reminders ("I missed an MOT and lost three days of earnings"), benchmarking ("am I making the same as everyone else?"), HMRC reconciliation ("I do not even know what HMRC has on file for me"). If you have a "this would be useful" thought, it has a real chance of becoming a feature.
- Gair