I Monetized My Ski App, Here's What Happened

Ski Pin Connect IQ Store Page

About Ski Pin

At the beginning of the 2026, I released a new data field for winter sports called Ski Pin. Ski Pin shows you the name of the ski run you're on, the run difficulty, and which lift is nearby. The CIQ app itself is straightforward, it gets your GPS coordinate and queries a custom web backend that checks the coordinate against OpenSkiMap data. Since there's a monthly cost to run the backend, I decided it'd make sense to monetize the data field to try to cover my costs. And I felt that the Ski Pin concept was unique enough in the CIQ ecosystem that passionate skiers may be willing to pay for the app.

I wanted to share my experience with monetization because I think it's valuable for other developers to see real numbers and understand if it's actually viable.

Monetization Math

For those who haven't looked into first-party monetization, there's a $100 annual fee and then a 15% service fee on all sales. At the beginning of the project, I didn't have a great understanding of how much the backend would cost to run. After doing some research I estimated that with modest adoption, it wouldn't be more than ~$20 a month. So my worst case annual cost would be around $100+$20*12months = $340/yr.

I really struggled with determining the price point for Ski Pin. I didn't want the price to be a significant barrier of entry, but I was eager to recoup my costs. To make $340, I would need to sell $400 in product to cover the 15% service fee. Since skiing is a seasonal sport, I figured a vast majority of my sales would occur in the first 4 months of the year, so I'd need to make ~$100/month. My goal was to make one sale a day on average. So monthly, $100/30 sales puts the price point at $3.33. I rounded that up to $4 to give some breathing room in case I didn't hit my target.

Ski Pin in the field

First Month Results

Looking back on January, two things worked in my favor. First, my backend cost estimate was high. My real cost was $8.46, significantly less than my $20 estimate. Second, I made a lot more sales than I expected! I sold 68 copies in January.

Below is a graph I'll be updating monthly with sales data. If I project out my monthly costs for the rest of the year with no additional sales, it looks like I'll still break even. That was my primary goal with this project.


January Sales Analysis

Lessons Learned

The biggest thing I learned is don't be afraid to price your app at what it's worth. I was genuinely worried that no one would be willing to spend more than $2 on a data field, and I almost priced Ski Pin lower because of that concern. But it turns out that if you're solving a real problem for a passionate audience, they may be willing to pay for it. Seasonal apps can absolutely work if you price appropriately for the condensed sales window, just make sure you're not leaving money on the table by undervaluing your work.

What do you think?

I'd love to hear from other developers who've monetized their apps, how did you approach pricing? Has it been worth it? And for those considering monetization, feel free to ask any questions about the process.

  • I can't even guess how many donations I've gotten for my apps.  Enough to upgrade to a new watch every once in a while...

    When I write an app. it's because it's something that I want. It's for me. If others like it, that's great.

    I do have apps with 100k to 700k downloads and I know of some other apps will well over a million downloads..

  • Very well sir, thank you for your hard work and support. 

  • I started out with low expectations still managed to be disappointed.

    ==============

    My timing was off (for one part). My app provided connection to a “big player” who also released an app at roughly the same time. My app even supported many more devices than their app. My app supports watches (the largest number of installs) when theirs still doesn’t.

    Part of my issue was finding ways of “advertising” the app.

    My app also provides (cool) features for my bike club and there’s not much interest there either.

    “Live and learn.”

  • If you build it for free and the community you should be happy and not disappointed.

  • I can't even guess how many donations I've gotten for my apps.  Enough to upgrade to a new watch every once in a while...

    That’s nice but (likely) you could get a new watch every couple of weeks working at McDonald’s.

    When I write an app. it's because it's something that I want. It's for me. If others like it, that's great.

    Or, you are just crazy

    This is a reliable justification (“making money” isn’t.) It’s (mostly) my reason too.

    I do have apps with 100k to 700k downloads and I know of some other apps will well over a million downloads.

    I think “early movers” had a big advantage. You also might have a “network effect” with users of your apps seeking out other apps you release.

    Given the number of apps now, it’s harder to be noticed. That seems very-much the case for watch faces.

  • If you build it for free and the community you should be happy and not disappointed.

    (This is contra your complaints about not making money.)

    In my case, not enough people are interested in it to have made the effort worth while.

  • Stop complaining and do more! 

  • ???

    I’m not complaining (you were doing that).

    I’m commenting here to say that making “real” money with IQ apps is very difficult (if not impossible). If that’s not your motivation, that’s fine!

    I have two Garmin-related apps for Windows that are paid. One is vaguely successful (but gets nowhere near to cover the cost of writing it.) The big advantage is that that experience is something people will pay you for.

    There aren’t any Garmin IQ developer jobs.

    I’ll support my apps and (maybe) add more features but I’ll otherwise find better things to do with my time.

  • You are complain and crying about your app. I stated a fact boy! Stop crying and move on.