from Hacker News

Ask HN: Sell, open-source, or abandon a $10k/year Mac app?

by EvanMiller on 1/8/15, 6:40 PM with 59 comments

In 2011 I wrote a low-end GIS program for Mac, called Magic Maps. The idea for the app was to make a simple, Mac-like alternative to ArcGIS and QGIS that makes it easy to plot points, import Shapefiles, and create chloropleth maps and animations without first wanting to open your veins in a bathtub.

It was my first desktop app, so the code isn't great, but it's found a loyal user base over the years has netted over $50k since 2011. Unfortunately, Magic Maps is now suffering from neglect and bit-rot, and some of the users are starting to revolt. At the very least, it needs a bit of work to fix crashes, ensure it works smoothly on Yosemite, etc.

I'd do this work myself, but I am putting all my time into another app, and as much as it pains me, I just don't have time to invest into Magic Maps any longer. I'm putting this out there because I'm honestly not sure what to do with the software at this point, and I'd like to hear other people's perspectives. I see my available options as:

* Open-source the project. I think open-source works well for a lot of things -- and I've done a lot of open-source work in the past -- but user-friendly software doesn't seem to be a good fit for open-source without ongoing sponsorship.

* Try to sell the project. This seems ideal, as I think there's potential for Magic Maps to be a viable business with a sufficiently savvy owner, but I'm not sure there's a market for code that doesn't include a developer or test coverage.

* Wind down the project and call it a day. This would be the least amount of work for me, but it hurts me to think about it. It just seems like a waste to throw away all that design and engineering effort -- it's a neat little package and I'd hate to put it in the trash.

Have other people been in similar situations? What did you do, and what do you think I should do? Sell it, open-source it, or call it quits?

BTW here's the Magic Maps home page: http://magicmaps.evanmiller.org/

  • by EvanMiller on 1/8/15, 8:52 PM

    I received an interesting reply over email which I wanted to share here. With the author's permission I've reproduced it below but blanked out some details:

    > I (or we as a company) faced pretty similar situation just a few weeks ago.

    > The app is called ______, and it was our first app ever, our child - app that constituted our company brand and still is pretty useful for many small business owners (_______ is an invoicing app, making something like $20k/year on our domestic market).

    > Unfortunately(?) business is business, so finally I decided to decline it. Now we’re making some final touches and will release it as open source project - again facing similar problems - the codebase is almost 6y old, app is not trivial, build procedure is not single click etc etc.

    > Besides all those risks and problems, I still believe that opening the source code is worth doing. That way we can help other (less advanced) programmers to start their own mac products/businesses. I’m sure that you’ll agree that after a certain point you need to look inside something bigger than a trivial app from examples folder, something that is/was a real thing, something ‘alive'. That’s IMHO a single priceless source of practical knowledge.

    > That’s my 10cents :)

  • by tjr on 1/8/15, 6:51 PM

    Not knowing all of the details, I'm not sure how reasonable this would be, but another possibility is to keep ownership of it, and pay someone else to fix bugs. The key question there is how much that would cost (in both your dollars and your time) vs. how much you are making on the application.

  • by debacle on 1/8/15, 7:55 PM

    I think one of the big problems with the app store model is that it creates this idea that you only pay once for software, ever.

    Your software doesn't have bit rot, it's just old. It was useful at one point in time and it is just a bit less so now. Consider the value proposition of a Magic Maps 2.0 to your users and what sort of feature list you could create. Decide an upgrade price point, and send an email to your users and create a newsletter allowing them to sign up for the new version. If you get 500 sign ups, cost out the features and have a freelancer develop them. If you get no sign ups, pack it up or sell it to someone.

  • by nthState on 1/8/15, 7:21 PM

    Many of us would love an app that was making $10k a year. That's a lot of money, can you do without it?

    If it was me, my financial situation may be different, but, I'd drag myself up by the scruff of my neck and set aside some time to fix it......$10k a year!

  • by echoless on 1/8/15, 7:31 PM

    I think there's another option. You could hire a freelancer and have him/her fix the bugs and get it working on Yosemite. Depending on the complexity of the code, this may or may not be feasible.

  • by harisamin on 1/8/15, 7:37 PM

    I’d be interested in collboarating/contracting if I could help. I just launched my first mac app http://mackernews.com You should also checkout http://sideprojects.assembly.com/

  • by hayksaakian on 1/8/15, 7:07 PM

    Have you considered hiring a contractor tonmaintain the code?

    If its generating a profit, maybe its worth it?

  • by gsands on 1/8/15, 8:25 PM

    I would fix it up.

    You get 3 benefits:

    1. Continued income from it (people aren't going to continue to buy it if the bad reviews keep coming in).

    2. You keep/improve your reputation. If your software isn't working well for any reason at all, it can give a bad reputation to the person/company attached.

    3. You increase the chances of a good buy-out in the future, over what it would currently bring now.

    We all know it can be difficult to get traction on a project, not to mention paying users. You already have proved this one can get both.

  • by tylerhall on 1/8/15, 8:21 PM

    I was in the same situation as you a few years ago. My Mac app was making enough money to be helpful but not quite enough to be worth the trouble. I seriously considered open sourcing it. But I stuck with it and, four years later, it grew and began supporting my family full-time.

    If you truly believe there's no chance of it ever growing larger, than by all means, retire it. I've sunsetted many apps that never caught on. But don't give up on it too soon!

  • by sbarker on 1/8/15, 7:42 PM

    Sell it. Get ahold of esri or partnersoft both have iOS apps yet lack Mac support unless you run a VM. It maybe a harder sell as most of the industries that use GIS data (power, telco, gov) use windows. Your are in a premo spot though because Partner and esri are both pushing iOS for outside guys/field workers quite a bit right now even if it's only a bullet point for them it could be a nice pay out for you.

  • by samspenc on 1/8/15, 9:04 PM

    Please don't wind down the project! I'm sure people are using it because they find it useful, and I think they would be disappointed if it stopped - I know I would if someone stopped working on an app I used heavily.

    (1) I think its worth trying to sell the app - you did a good job, obviously it has a user base, and I think its fair you get paid for it and have someone continue to maintain it.

    (2) If that's a hassle and you lose control of the project's trajectory - why not open-source? Your users would still use it, it would be free, and there might be some power user willing to take it on and improve the code base.

    (3) As someone else mentioned in the comments below, maybe find a contractor to maintain it? This only makes sense if the cost of the contractor is less than what you're making off it, of course.

  • by opless on 1/8/15, 6:45 PM

    I'd consider selling it. I'm sure there's a 100lb GIS gorilla that would snap you up. Have you tried waving it at them. I'm afraid the only one I know is MapInfo who I'm sure got bought out by Pitney Bowes back around 2005?

  • by revorad on 1/8/15, 10:41 PM

    You could hire someone. I know you might find it hard to let go of your codebase and feel it's too complex, but there are plenty of good programmers out there.

    You said you're concerned about how much it might cost. Surely you can afford to try someone out for a short amount of time, given the app makes $10K a year. If you shut it down or open source it, that income's gone anyway. So why not try to keep a good product alive?

    One good place to look for a programmer might be the monthly HN threads by whoishiring - https://news.ycombinator.com/submitted?id=whoishiring

  • by glasses on 1/8/15, 7:47 PM

    What about letting someone take over the project but you get to keep a share of the profits for guidance and advice (30% or so).

    It benefits both parties, you know what features the project needs to implement and what direction it needs to take to make more money, while the new owner/developer gets ramped up. You guys can even agree to a one year period of help and then separate, but at least the project keeps running and making money.

    Not sure if this is usually done, but it seems like everyone wins :)

  • by Mnwhlp on 1/9/15, 9:34 PM

    Why don't you pay me to update it and keep half of the profits. That way you get to keep control of the app and half of the profits while I do all of the work. I made this public because I think it's a good alternative for you even we don't end up working together. But hey PM me if you're interested.

  • by bdcravens on 1/8/15, 7:20 PM

    How much time do you put into it each year? You need to subtract that time from your yearly revenue.

  • by v_ignatyev on 1/8/15, 9:37 PM

    Try to receive funds and make business from it: hire developers, create few updates, try to expand onto new markets etc. and then try to exit this business.

    Or just throw off this project and focus on another one. It's old. It's kind of liability not a money generator.

  • by thelollies on 1/8/15, 7:33 PM

    Just saw this on the front page, seems like a good option (get others to work with you and share the profit): http://sideprojects.assembly.com/

  • by ErikRogneby on 1/8/15, 8:31 PM

    This just showed up on HN: http://sideprojects.assembly.com/

    Crowd source further development and continue to participate in revenue and product direction.

  • by blyxem on 1/9/15, 12:33 AM

    With that amount of revenue, you could easily outsource it to an offshore dev and claim back a lot of your time, while still retaining ownership of the app and IP.

  • by cdvonstinkpot on 1/8/15, 7:06 PM

  • by emilburzo on 1/9/15, 9:52 AM

    How sure are you about your other app? (the one you're investing your time in currently)

    It might be unwise to give some certain away for something not so certain.

  • by eric_bullington on 1/8/15, 7:17 PM

    It looks like a really cool project that you've already done a lot with, but also with a lot of potential.

    Are there many active competitors?

    Is it written in all Objective C?

  • by harisamin on 1/8/15, 7:35 PM

    i just recently launched my first mac app http://mackernews.com $10K/year sounds great. Ideally I’d like to get to that stage. Are there a lot of crashes that you’d like to fix or mostly Yosemite style UI updates or both? I would be interested in collaborating/contracting

  • by eddie_31003 on 1/8/15, 8:38 PM

    It would be nice to see it Open Sourced, but I agree that it will fall to the wayside without ongoing sponsorship.

  • by ca98am79 on 1/8/15, 8:49 PM

    Have you considered selling it on Flippa?

  • by porter on 1/8/15, 8:22 PM

    How much do you want to sell it for?