Why We Don't Gamify the Outdoors

There is a default playbook for consumer apps now. You ship a streak counter. You ship badges. You ship a leaderboard, a feed, a kudos button, a weekly recap that arrives every Monday at 9 a.m. You ship push notifications that say “Your friend just logged a workout” and “You’re three days away from a new milestone.” It is a good playbook. It works. Retention curves bend up and to the right. It is also, for an outdoor app, exactly wrong.

We thought about all of it. We tried some of it on paper. Then we threw it out, on purpose, and decided to be honest about why.

Strava is a good company building the wrong thing for us

Strava is excellent at what it does. It turned running and cycling into a shared, legible practice, and it gave millions of athletes a structure for showing up. We are not here to dunk on Strava. We are here to say it is a different kind of product than ours. Strava is a social fitness platform. Baseline Maps is a quiet field tool. The choices that make one great would make the other unbearable.

What gamification actually optimizes for

Streaks, badges, and leaderboards do not exist to make you a better angler or hunter or hiker. They exist to make the app the thing you think about. Every game mechanic on your phone is a small, polite hand pulling your attention toward the screen and away from the room you are in. That is the design intent. When the room you are in is a river at first light, the cost of that hand is not small.

Why streaks are the worst feature for outdoor apps

A streak is a promise that punishes you for stopping. Outdoor sport is already seasonal, weather-dependent, and shaped by life — a sick kid, a closed road, a smoke advisory, a deployment, a funeral. Building a feature that rewards uninterrupted use is building a feature that argues with reality. We will not ask a user to choose between a streak counter and a closed season. The water does not care about your streak. Neither do we.

The notification we never send

There is one notification we have promised not to ship: the engagement nudge. We will not send “you haven’t opened the app in five days.” We will not send “your friend just logged a catch.” We will not send “you’re close to unlocking something.” The notifications we do send are about conditions changing in the field — a flow spike, a regulation update, a weather window opening. If the phone in your pocket buzzes, it is because the world moved, not because our metrics did.

What we measure instead of engagement

We do not have an engagement-minutes goal. We never want one. The numbers we watch are these: do people renew, do they request features that show they trust us with their season, and do they actually plan trips inside the app rather than just browsing it. If a user opens Baseline Maps for ninety seconds on a Thursday night, checks tomorrow’s flows, and closes it satisfied, that is a perfect session. We will never try to stretch it.

The social features we kept

We are not anti-social. We are anti-feed. You can share a flow chart with a buddy in a normal text message. You can hand off a waypoint to someone meeting you at the put-in. You can log a fish to a private journal that nobody else sees unless you choose to send the entry. There is no follower count. There is no public leaderboard. The social surface is the same one you already use with the people you actually fish and hunt with.

What ‘calm software’ means in the field

Calm software, for us, means the app earns its place by being useful when it is open and invisible when it is not. It means no celebration animations when you save a waypoint. No haptic confetti. No tutorial that ranks your profile completeness. The interface is dark enough to read at dawn, quiet enough to use one-handed in a boat, and honest enough to admit when data is stale. The reward for using the app well is the trip itself.

Where this philosophy will get tested

We know this is easier to write than to hold. The pressure to add an engagement mechanic does not come from a villain in a meeting. It comes from a flat retention chart and a quiet quarter. Some week, someone will say “what if just a small streak, opt-in, just a little one.” That is the moment this post exists to argue with. We are putting it in writing now so we can lose that argument cleanly later, in public, with a record.

There is a version of this app we could have built that would be more “engaging” by every standard metric in the industry. It would have a feed. It would have streaks. It would have a weekly email that ranked you against people who do not fish the same water you do. It would have a public profile, a follower graph, a heatmap of your favorite runs visible to strangers, and a tasteful little flame icon that turns gray on the day you skip. It would probably have better retention numbers in year one. It would also, in year three, be one more reason people put their phone down with a sour taste and step outside.

The strange thing about the engagement playbook is that it works on the people who need it least and fails on the people who need an outdoor app most. The angler who fishes every weekend does not need a streak to remember to fish. The hunter scouting a unit in August does not need a badge to remember to scout. The people we build for are already motivated. Adding a points system to that motivation is like adding a metronome to a heartbeat. It is condescending at best and corrosive at worst.

The outdoors is the last place in most people’s lives where attention is not being mined. The river does not have a notification system. The ridge does not gamify the climb. The fish do not award badges for consistency. The whole reason any of us go out there is that the rules are different — slower, older, more honest. An app that ports the engagement playbook into that space is not adding value to the trip. It is taxing it.

We would rather build the smallest possible useful thing. A map that loads offline. A flow chart that tells the truth. A regulation page that is current. A journal that is private. A handful of intel briefs that respect your time. That is the entire product surface, and it is the entire product surface on purpose. Every feature we have not shipped is a feature we have actively decided not to ship, and that list is longer than the one in the app.

If you came to Baseline Maps from a fitness app or a social tracking app and you find yourself waiting for the dopamine hit — the badge, the kudos, the streak fire emoji — we understand. That is what every other app has trained you to expect. We are not going to give it to you. What you will get instead is an app that, on a good day, you barely notice you used. You opened it. You checked the thing. You went outside. That is the whole loop.

We will hold this line for as long as we run this company. The day we ship a streak counter is the day we have lost the plot, and we want our users to be the ones who tell us.

If a feature ever shows up in Baseline Maps that pulls you toward your phone instead of toward the water, tell us. The Development Queue is the place. We will reverse it.