Tuesday, Jun 10, 2025 at 15:47
Thanks for your thoughtful question — I've only just seen this now. We completely understand the appeal of native Android Auto or CarPlay integration, especially for ease of in-dash use during travel.
We’ve certainly explored these possibilities, but there are a few key reasons why we’re not currently planning to release a separate app version specifically to meet the requirements for Android Auto or CarPlay approval:
1. Strict Platform Limitations
Google and Apple both impose heavy restrictions on what functions a navigation app can offer through Android Auto and CarPlay. Our app,
ExplorOz Traveller, offers a rich feature set that goes far beyond what’s permitted on those platforms — including offline map layers, detailed point-of-interest tools, user-generated content, custom route planning, and more. To comply, we’d have to strip out a lot of core functionality and redesign the app from the ground up, essentially building and maintaining a separate product.
2. Cost vs. Benefit for Our Niche
Creating and supporting a CarPlay/Android Auto app involves substantial development, compliance testing, and ongoing maintenance. Our focus is on delivering the best possible solution for Australian travellers, especially those heading into remote areas. Given our user base and the current technical limits of these platforms, the return on such a major investment just doesn’t stack up at this time — especially when other practical workarounds already exist.
3. We Prioritise a Truly Portable Solution
Our core mission is to provide a fully portable and flexible navigation tool — not just for drivers, but for hikers, cyclists, motorcyclists, and anyone exploring Australia off the beaten track. Unlike systems locked to in-vehicle displays, the Traveller app runs across phones, tablets, and even laptops, so users can take it anywhere, whether they're walking a trail, riding a bike, or setting off in a 4WD. This flexibility is one of the app’s key strengths.
4. Alternative Options Already Exist
As you’ve noted, devices like Carlinkit or Android Auto boxes aren’t perfect — but they do offer a way to display the full functionality of the Traveller app on your vehicle screen, without giving up the features that matter most for off-
grid navigation. While not as seamless as native integration, they maintain full offline support and map detail, which is vital for Australian touring.
5. Shifting Industry Direction
Interestingly, we’re also seeing some major car manufacturers moving away from integrating CarPlay or Android Auto into their systems altogether. Tesla has always opted out, and more recently General Motors (GM), BMW (with iDrive 8), and others have signalled similar moves. Their reasoning often relates to maintaining tighter control over vehicle interfaces, data, and safety systems — especially as cars shift toward fully autonomous functionality. At the same time, Android-based adapter boxes are growing in popularity globally because they overcome many of the functional limitations of built-in head units, and aren't restricted to just navigation apps. The automotive tech landscape is evolving quickly, and it's always interesting to see how both consumers and manufacturers respond.
We’ll continue to monitor how the Android Auto and CarPlay platforms evolve, and we’re always open to re-evaluating if the constraints change. For now, our focus remains on ensuring the core app delivers outstanding capability and reliability for remote navigation — across all modes of travel.
Thanks again for your interest — it’s great to hear that you value the advantages of
EOTopo and the Traveller app for Australian use!
Michelle
AnswerID:
648110