¿Quieres una función de Garmin que aún no existe? Así es como conseguir que la construyan

Ahora hay un tablero público de ideas donde cualquiera puede enviar solicitudes de funciones para mis apps de Garmin, ver lo que otros han pedido y votar por lo que se construirá después.
Day 53: The Public Idea Board Is Open
If you've ever used one of my Garmin apps or watchfaces and thought "this would be so much better if it could do X" — this is for you.
I build watchfaces, widgets, and data fields for Garmin. Over time, people have sent me ideas from everywhere: Connect IQ Store reviews, Instagram comments, emails, DMs. Great ideas, spread across a dozen different places, with no way to see if someone else had already asked for the same thing.
The old system was a mess
I used to track feature requests in a text file on my laptop. Nobody could see it. Nobody could add to it. I had no way to know which ideas were popular and which were one-person wishes. I'd build something, and then find out three people had asked for the exact same thing six months earlier and I'd missed them all.
That's fixed now.
The public idea board
There's a public feature request board where you can:
- See every open request — across all my apps, sorted by vote count
- Vote for what you want — if someone already asked for your idea, just upvote it
- Submit new requests — if your idea isn't there yet, add it
- Track the status — requests are marked Open, Implemented, or Not Possible
If something is marked "Not Possible", there's usually a note explaining why — often a hardware limitation, a Garmin API constraint, or something that would break other features.
How the build queue works
When I sit down to plan an update, the vote count is the first thing I look at. A request with 40 votes gets prioritised over a request with 3. It's not the only factor — some things are quick wins regardless of votes, and some technically complex requests need more thought — but it's the main input.
This matters because it shifts power to you. If you want something built, get other people to vote for it. The more visible a request is, the faster it moves.
What makes a good request
The best requests are specific. Not "make it better" but "show the time to sunrise on the lock screen." Not "add more data fields" but "add a field showing normalized power for cycling." The more specific you are, the easier it is for me to scope, build, and ship it.
You'll need to enter an email address to vote or submit — this is just to prevent spam, there's no account or password. A one-click verification email is sent the first time.
Go to the idea board →Únete a la Garmin School
Deja tu correo electrónico para acceder a la Garmin School y recibir actualizaciones sobre nuevos videos y apps.