Testers wanted: free offline motorcycle nav for Android (UK)

phpboyscout

Member
UKGSer Subscriber
Joined
Nov 16, 2026
Messages
6
Reaction score
4
Location
Stockport. UK
Hi all. Thanks to the mods for letting me post this.

I’ve built a motorcycle sat-nav app for Android called Ridelark, and I’m looking for UK riders to test it. It works on any bike. It began because the app that came with my Enfield drove me mad, but it isn’t tied to any make.

What it does, all free:
  • Routing and place search with no signal, on offline maps
  • Spoken turn-by-turn directions through your headset
  • GPX tracks, saved places and saved routes
  • Speed limit warnings
  • Ride recording
There’s a 37-second look at it here:
(apologies for the AI'ness of it, it was done in a hurry)

No account, no adverts, and nothing to buy in the beta. You open it and ride.

Your data stays on your phone. There’s no telemetry or tracking in the app. Your routes, places and rides never leave the phone unless you choose to share a ride with me to help debug a problem.

Will it always be free? Everything listed above, yes. That stays free. At some point there’ll be a paid “Plus” version, for features that need servers or AI behind them, because those cost money every month someone uses them. Hosting the maps already costs me more than the app brings in, so Plus is there to cover running costs, not to put the basics behind a paywall. There’s no price yet, and nothing will go on sale until those features actually work.

What I’m asking: use it on your normal rides for two weeks and tell me what’s broken, confusing or missing. Google needs 12 testers opted in for 14 days in a row before the app can go public, so staying in for the full fortnight helps as much as the feedback does.

You’ll need an Android phone on Android 12 or newer with Google Play, and to be riding in the UK.

Getting in takes two steps. This is the only sign-up involved, and it’s Google’s, not mine:
  1. Join the testers’ Google Group with your Google account: groups.google.com/g/ridelark-beta
  2. On your phone, open play.google.com/apps/testing/app.ridelark, accept, then install from Play.
The full walk-through is at ridelark.app/beta

iPhone? Not yet. If the Android beta goes well, an iPhone version will follow shortly after. Testing on Android now is the quickest way to get there.

Known rough edges. It’s early. Arrival can be called a bit before you’ve actually arrived. Like most phone navs, a spoken direction will cut into a helmet intercom conversation. Fixing that is on the list, not done.

Other displays wanted. If you run a handlebar display or a dedicated unit other than a Royal Enfield Tripper, I’d especially like to hear from you. Ridelark only talks to the Tripper so far, and I can only add others with help from someone who owns one.

Feedback in this thread is fine, or through ridelark.app/support if you’d rather not post. Thanks for reading.
 

Attachments

  • ridelark-planned-route.jpg
    ridelark-planned-route.jpg
    50.4 KB · Views: 6
  • ridelark-navigation-roundabout.jpg
    ridelark-navigation-roundabout.jpg
    54.2 KB · Views: 7
Well good on ya for developing this app, but without wanting to be a wet blanket, what does it offer that something like DMD2 doesn't? I'm using this on my current tour and it is monsterously powerful - almost too much - but it certainly offers routing, location saving, GPS routing, spoken directions etc etc.
 
Not a wet blanket at all, it's the right question. I'm going to answer it at some length, and on purpose: you won't be the only one weighing Ridelark against whatever is already on your bars, so I'd rather put it all out there in one go.

If you're happy with DMD2, keep it

DMD2 is a seriously capable bit of kit, and so are a few others like it. If you tour abroad, ride trails, want bike data on a screen in front of you, or like to tune every part of your setup, those apps do things Ridelark doesn't and isn't trying to.

What Ridelark is for

The rider who wants to plan a ride, put the phone in a pocket and not touch it again. Directions come through your intercom, with a warning before the speed limit drops. At a planned stop it counts down and carries on; press your helmet's play button if you want longer. There's no dashboard to set up and very little to configure. You said DMD2 is almost too much, and that's exactly the gap I'm going for.

What it does today

- Routing, search and spoken directions all done on the phone, so it works with no signal.
- Free maps for the whole UK, downloaded by region.
- Search by place, street, address or postcode, or drop a pin.
- Stops along the way, and an option to avoid motorways.
- Import a GPX track and follow it.
- Records your rides to the phone, not to a server, and shares one as GPX when you ask.
- Shows the next turn on a handlebar display if you have a supported one.

Privacy

A nav app knows everywhere you ride, so it's worth asking of any of them. Ridelark has no account, no adverts, no analytics, no tracking and no crash reporting built in. Your live position is never sent to me, and your rides, places and routes stay on the phone.

A few things do go online, and this is all of them:

- Map downloads come from my servers, once Google Play has confirmed the app is a genuine copy. That includes the maps along a ride you plan, so the server sees roughly where that ride goes. There's no account to tie it to, only a random number the app made up.
- The full map you see when reviewing a route, and "Search online" if you tap it, use outside services: OpenFreeMap, komoot's Photon and your phone's own geocoder, which is usually Google's.
- Feedback goes only when you write it and press Send, and the screen shows you exactly what's in it first. It comes to me and nobody else.

The full detail is at ridelark.app/privacy.

What it doesn't do (yet)

- Anything outside the UK.
- iPhone. It's Android 12 or newer only.
- Off-road or curvy-road routing.
- Bike data, group riding, weather or roadbooks.
- Android Auto.

It's also in closed testing, so expect rough edges. Finding them is the point.

Where it's going

Being worked on next: fuel and coffee stops along your route, and more roads to avoid (tolls, ferries, unsurfaced). Being thought about: curvy roads and round trips, a word of commentary about the road you're on, sharing directions with a pillion (without needing a paired intercom), more handlebar displays and Android Auto, and iPhone. None of that has a date, and what riders ask for will decide the order.

How I'm building it

I'm one developer. I can't build the kitchen sink for launch, so I'm not trying to. The plan is to get the basics right and then add what riders actually ask for and use, which is a big part of why I'm after testers.

Two things I can commit to. There's no hardware to buy: it runs on the phone you already have. And the maps are free. It's UK only while it's in testing; more regions follow after, and they'll be free too.

So: if you want a dashboard, there are better tools than mine. If you'd rather have something you set up once and forget about, I'd love you to try it and tell me what's missing.
 
What I’m asking: use it on your normal rides for two weeks and tell me what’s broken, confusing or missing. Google needs 12 testers opted in for 14 days in a row before the app can go public, so staying in for the full fortnight helps as much as the feedback does.

what timescale are you looking to complete this? Mid November seems an odd time of year to ask riders in the UK to test this for 2 weeks as you have a small pool of active riders to draw from.
 
OK, sounds good. DMD2 is almost too much, but the graphics work well for me (I'm colourblind). Unfortunately I will be arriving back in the UK about a week from now and then have a couple of days to get home and that's it until spring, but I hope this goes well as my brain struggles with the complexity of DMD, and I cannot see the value in a Garmin these days.
 
what timescale are you looking to complete this? Mid November seems an odd time of year to ask riders in the UK to test this for 2 weeks as you have a small pool of active riders to draw from.
You're right in that it's a bit of an odd time, but I've no set timeframe in all honesty. Granted its a small pool, What I'm after is any feedback that anyone can give, even if its only from a single ride. It all helps me to iron out bugs and to get any kind of indication that the app does what it says on the tin, and does it well enough that I can actually feel confident to launch it. Plus it gives me a chance to get a feel for any features that it needs that I've not already got in my roadmap.

Also it gives me a chance to reach out to anyone willing to do some testing with one the following screens so I can see about getting Ridelark working with them
  • Royal Enfield Tripper Dash
  • BMW Motorrad Connectivity TFT
  • Triumph My Triumph Connectivity
  • KTM MY RIDE / KTM Connect
  • Ducati Multimedia System
  • Honda RoadSync
  • Yamaha Y-Connect / Garmin StreetCross
  • Kawasaki Rideology
  • Beeline Moto II
  • Garmin zūmo sat-navs
  • An Android motorcycle tablet, such as a Carpe Iter
  • A Wear OS or Garmin watch
BTW the two weeks is more a case of "install the app and don't uninstall it for two weeks". The T&Cs for publishing an app on the google play store as an individual requires at least 14 people are on the test program, have installed the app (ideally using it) and not uninstalling it for 2 weeks before I can take it to public testing and then launch it properly. TBH, I'm not so worried about that part as much as I am about getting some real feedback about it
 
OK, sounds good. DMD2 is almost too much, but the graphics work well for me (I'm colourblind). Unfortunately I will be arriving back in the UK about a week from now and then have a couple of days to get home and that's it until spring, but I hope this goes well as my brain struggles with the complexity of DMD, and I cannot see the value in a Garmin these days.
no worries... and you have already given me an important piece of feedback I didn't even know I needed... I hadn't even considered colourblindness in the design. So thats a lucky accident and one I'm glad to have learnt about now :)
 
Is there any reason why testers cannot or shouldn’t test the app in their car or on a bicycle?
 
Is there any reason why testers cannot or shouldn’t test the app in their car or on a bicycle?
No reason at all, it can be used in any way that suits you. It's tailored for being on a bike of some kind (motor or human powered) as its more about the audio navigation than following a map on a screen but it should work just as well as one with a map to follow.. I've been testing it in my car on journeys, as well as when I'm out on my bike, and I've had no issues
 
Last edited:


Back
Top Bottom