78
102 Comments

Is it worth building an app just for me?

I'm currently in the process of building a mobile app. The likelihood of making money from this app is slim. At the very least, this project is something that means a lot to me, since this product is something that I myself need in my life.

The app is a customizable personal wellness tracker that is entirely private. It seems silly, given how saturated this space is. But I've personally felt a lot of frustration with the health/wellness trackers that currently exist in App Stores. They are either far too cluttered, in partnership with some corporate entity with whom I do not want to share my health data, or lacking in customization options.

My goal is to build the product that I currently need in my life and can't seem to find in the App Store.

I struggle with the idea that it is "pointless" to build an app that meets the very specific need of only one person (me). Is it worth the time, effort, and frustration to build an app that probably won't make me a dime?

At the same time, the level of delight it would bring me to create the product that is missing from my life might just validate the whole endeavour...

I'll be posting more about my app development peaks and valleys on my blog (N.B.: right now it's just stuff about my cat).

  1. 27

    Go for it!

    You've mentioned that the apps in the space are "either far too cluttered, in partnership with some corporate entity with whom I do not want to share my health data, or lacking in customization options".

    Have you thought about the reason for this? IMO a good % of those apps probably started simple. Then (as they gained in popularity), they probably:

    • Got a lot of feature requests (and found the more features the offer, the more people want to buy their premium memberships)

    • Needed to partner because they couldn't easily monetize the app, and found that selling data/partnerships is an easier option to make $

    B2C mobile apps are really tough. I've analyzed 490+ founder interviews and there were a few B2C mobile apps and many of them said something like this:

    I poured three months of all my free time into this app, and reading feedback from some users who complain about having to pay for the upgraded version of the app because they say they can get the charts free from the doctor's office was exasperating. I'm thinking about what I can build next to target businesses instead.

    Based on this, I'd assume the real reason for the clutter/partnerships/selling data is simply because these apps found it really, really hard to get money from actual users.

    1. 1

      thanks for the insight

  2. 1

    You were immersed in this process and forgot your original intention. Your original intention should be to serve specific customers rather than your own

  3. 9

    Hey,

    when I started my own app Maxout in April during lockdown, I was in the same situation. I just wanted an app to schedule my workouts but all the apps on the market were either really ugly, too complicated and time consuming to use or not that much better than pen & paper (what I was using at that time).

    So, I went ahead and built that project. And for months, I used it for myself only. But over time, people noticed that I was sharing something in my Insta stories that looked good and I seemed to use often, so people started asking questions about it.

    This made me opening it up a bit and now I'm building it out to invite more users. For a few months, I will try it out if it's worth it.

    But you know what? If it isn't successful, I will still keep the app and keep on going because I'm in love with what I have and I use it every single day right now <3

    1. 4

      This is very inspiring!

    2. 1

      I have read your farewell post on site of your app Maxout, and it was even more instructive then your this comment, thanks! Did you manage t0 find or learn a better validation method?

  4. 9

    You absolutely should build this. Launch it without the expectation of any users besides yourself and document your learning process as you build. Engineering and building things is an inherently creative process. Not all creative processes need to make money. In your case, it sounds like you are going to gain value from the app in addition to it being a creative outlet.

    I wrote about the idea that building things doesn’t always have to be about making money or starting a business. You can build to learn and to create.

    1. 2

      I think when you're only focused on money you lose the creative motivation that got you making it in the first place.

  5. 2

    Hi @alexhaynes, I have been struggling with the same question for last one month. And there are two parts to the answer which I have found

    1. Validate the problem: this part is not easy as it sounds because people even themselves dont know what they want. Specially until you build an MVP, it's hard to assess the idea.

    2. Learn to enjoy the process: I am currently building StyleScan, an app for discovering multiple fashion products at once. I started working on this because shopping online became hard for me, specially with lots of websites, options. It was a time consuming process. Since I started building my interest in the problem has also diminished because I don't shop that often :P. What kept me going is that learning in this project. I am building search stack, using LLMs to understand query, building UI, etc. And this learning is what I am enjoying and is keeping me going. I still don't know if the problem is worth solving or not. If someone can add to it, I would really appreciate it. But since I am enjoying the process I am continuing to work on it.

    Hope this helps.

  6. 5

    If the time and money you loose on it doesn't impact you negatively, then definitely go for it. Even if you don't plan to monetize it right now doesn't mean that it won't become worth monetizing in the future. It may happen, that once you build it you'll discover other people who will also see the value in it. And even if that doesn't happen you can still get a lot of learning out of it.
    I also build things just because I need them and that I don't plan on monetizing, like this Chrome extension. Sometimes the need to scratch your own itch is just stronger 😄

    1. 2

      Completely agree with you! Cost-wise, all I can imagine is having a cost for the app developer program. So completely like catico said, it might be nice going for it just for your sake and creating something cool and that will be useful for you :)
      @catico cool extension :D

  7. 5

    I'd say yes it is. At best, there might be other people like you and you'll make some money. At worst, you'll solve your own problem and have a product that makes your own life easier. You'll also have a great portfolio piece and subject to talk about in any job interviews. Not to mention what you'll learn from taking a project from inception to release. It's really really hard to follow through on a project idea.

    I made Chapter24 (https://chapter24.app) for myself. The product philosophy and every feature is designed just "for me". I didn't do any user research or anything and I still don't have any paying users. However building and launching the project was incredibly good fun. I'm also motivated to write on my own blog now because it's powered by Chapter24 and I built the product just so I could use it to write a blog 😂

    So I'd definitely say, go for it!! What the worst that could happen? You'll end up with a finished app on an app store. Not a bad result at all :)

    1. 1

      HI ayush, Chapter24 looks great and easy to setup. I'm wondering how you managed to connect custom domains?

      1. 1

        Thanks @gieoon! I'm using CloudFront as a cache layer in front of all the hosted blogs. So for a custom domain, I just configure CloudFront to use the user provided custom domain and then I show the user the DNS config to point their domain name at the CloudFront distribution.

        Hope that made sense?

        1. 1

          Yup, that sounds amazing. Thanks.

  8. 4

    @lexhaynes This is actually how I started my venture. I had a personal pain point and the current solutions just were not working for me. I created an application that I wanted to use and turns out a lot of people I showed it to wanted to use it as well. The best thing you can do is start. I'd highly suggest you go for it. If you need any help at all, feel free to reach out to me!

  9. 4

    Hi Alexandra! I built my first mobile app for myself & now there's over 6k MAU. It doesn't pay the bills really but it helped me get my last job & it helps me immensely in other ways. I've had amazing conversations with 100s of users from all over the world that were seeking tools to better their mental health.

    The market will always be saturated in wellness, but if you truly care about the product & your users (including yourself) & can iterate the product over time it could turn into a much bigger thing than you can imagine. Hope that helps!

    Have you joined the Mobile group here on IH yet? Would love to have you join & share questions or content about your mobile app journey :)

    1. 2

      Thanks for the inspiration! I haven't joined the mobile group but I will now!

      1. 1

        Awesome @lexhaynes! All the best getting v1 of your app launched!

  10. 3

    So there are lots of comments below, but I thought to share my thoughts on this matter and use some references I think are important.

    You mention that:
    "I struggle with the idea that it is "pointless" to build an app that meets the very specific need of only one person (me). Is it worth the time, effort, and frustration to build an app that probably won't make me a dime?"

    Well if you build something you yourself want, you've already achieved two successful points:

    1. You have 1 user (you!) Congratulations! 👏 Sounds silly, but even Airbnb at the beginning was used by just a handful of people, including the founders.

    2. You've validated the problem. This is the most important point! Back to the Airbnb example, they started it because they needed money to pay their rent. And after running out of money, they solved their problem but renting out air mattresses from their apartment.

    Many people never get to this stage of validation at all, so go ahead and build it!

    On the other hand, if you build something you are motivated about, that you're curious about, and excited to use, this will push you to move faster, build better and eventually, make something (hopefully) valuable for others. Yes, there is no unique way to validate if other people also have this problem, but there are a bunch of ways you can try to use to answer this. Mainly by talking with other people:

    If you're potential users hang out in physical places, go there and talk to them, if they hang out in digital spaces (like Indie Hackers, social media, forums, groups, etc.) go there and talk to them. I'm always happy to support and help, and I'm sure others will too.

    Finally, Paul Graham (co-founder of YC) has a fantastic essay about making great work. It's long (took me over 2 hours to fully read and pay attention to all details), but it is extremely valuable and full of insights. I felt identified from beginning to end. And talks exactly about this: follow your curiosity.

    "Curiosity is the key to all four steps in doing great work: it will choose the field for you, get you to the frontier, cause you to notice the gaps in it, and drive you to explore them. The whole process is a kind of dance with curiosity." - Paul Graham. I can't post links yet but check out his website and search for "How to do great work".

    Hope this helps. Keen to connect, build and help more entrepreneurs succeed together.

  11. 3

    Hi @lexhaynes, I say go for it! There's a reason people forever have been pottering in the garden shed or building ships in bottles. Building for yourself, learning and enjoying your craft can be very rewarding.

    I just arrived here because I've been building https://braintool.org for my personal use over the last couple of years and am now thinking maybe its good enough for other people to enjoy also.

    I'd say the key for a software project is that the first step is small enough that you can get to an MVP-For-Me stage without too much frustration. After that its all gravy!

    Good luck,
    Tony

    1. 2

      That is such an awesome answer, and one I had never really thought of before, but its so logical.

    2. 1

      Wow, beautify that interface and this may be very profitable!

      1. 1

        Thanks @shockwave ! The beautify part is definitely a challenge!

  12. 3

    You should definitely build it. Not only you will enjoy the whole process of building something which is going to solve one of YOUR need, there are some chances that there exist people who will like it as well.

    Take my project, Designtack, for example. I didn't know if it was something people would need because there already exists giant alternatives but I was happy that it will solve my problem of content marketing. Turns out, I have people paying for the tool I built and I use.

  13. 3

    No brainer. Build it. You will learn a lot, it will be challenging and you will get a lot of satisfaction from doing it. Also, 'The likelihood of making money from this app is slim' is an untested assumption.

    Do you want to make money from building an app? If yes, then the best way to do this, is find and speak to others who are also frustrated with the apps in the market. You can easily do this through ethnographic research (observing peoples behaviour). Read the reviews of the app, particularly the bad ones. Who else feels your pain? Find online communities and reach out to people, speak to them.

    As per others on the thread, happy to help with advice etc, don't hesitate to reach out. Best of luck, look forward to hearing how you get on!

  14. 3

    Yes, as you said, it starts with a personal problem that you want to solve (e.g. repetitive work, etc.) or things you want to improve in your self (e.g. health, habits, learn faster, etc.).

    I, for example, have stuggled with social media addiction which affects my productivity a lot, so I created an app (https://dailynewsound.com) to fix it. It goes back to fundamentals really, and the fact that you experience it, means that others do as well.

    What you could also do is to add content (e.g. blogs or posts) and dig deep around your problem you are working on (fitness), strong enough that people will take notice.

    It also helps to frequently get feedback from IH community, as to how you can improve your product. But you'd still go with your gut feeling and later on, the user data/feedback to make your decisions.

  15. 3

    I would say it is worth it if you enjoy developing the app, otherwise it probably isn't. You should also not forget the knowledge and skills you will develop along the way, that can be invaluable! Enjoy the process and think of all the things you will learn, at the end of your journey you will have a tailored app as a bonus! That said, the perfect answer is to find something you enjoy working on, enjoy to use and can be enjoyed by others.

    1. 2

      It's so easy to get caught up in the idea that nothing has value unless it makes money. But doing something for the joy of it, especially in a year very much lacking in joy, is starting to feel more worth it :)

  16. 1

    Hi @alexhaynes, I build www.chessdejavu.com mainly for myself to learn chess openings as I find it really hard to remember all the opening moves. With this app I can train like you would train for a marathon. I find it really helpfull since other chess apps don't do it like I prefer.

    Ofcourse as a IH i'd like to get some revenue with it which I failed at until this far, but creating it, thinking about it, validating it helps you for your future projects. On my next project I would validate my idea first before coding anything. But still I wasn't able to create a website or app before. Now I know how to, so the next time I have a validated idea I know it won't be a roadblock, something to worry about.

    Good luck!

  17. 2

    i think if its a product you need and you like build stuff its whort it build

  18. 2

    In my opinion, if you are building it by yourself, without outsourcing it. That's worth every single second you invest in. Because,

    1. You can learn new things + expand your portfolio.
    2. You can pull a lot more value out of it.
    3. It's your app. You can do whatever you want.
    4. you can also generalize the app a bit with another version and push it to the marketplace. But I will not suggest pushing too hard in the fitness industry. Maybe just publish it and leave it.
  19. 2

    As others say, if the project will help you in your life, why not do it?

    Moreover, why ban even before the creation to potentially monetize in the future (even if it is not the basic plan)?

    And even if it's not your plan to monetize it, why not do it to strengthen a professional portfolio or even as a personal accomplishment?

    (I don't expect to have an answer since the post is quite old, but I really think that these questions can help people who are in the same position.)

    1. 1

      Yes, thanks, I am in a same position, I mean one of my app ideas. And now I am on a step or a half-mile further on that road:
      I made an Android app for it as my personal solution of the very similar problem and similar concerns;
      I made it based on some raw open source app, and initially it helped me a lot to scratch the itch and give solution to a problem, but overall the app has its limitation due to problems in upstream code -and yet I can't create product based on open source (well, not finally sure on this exact point, but yet I believe in that. )

      So now I am at point of deciding what to do with all this, I either will start create a new app from "zero", or... well, the necessity is strong, and the fact that I solved the privacy concerns is also a strong motivation.
      What hinders this path is realization or recognition of the fact that I would not be able to make sells with this app, because the space is even more crowded then one of OP ...well these apps are crappy anyway, almost all of them, and at least all top apps in domain. But these companies have huge marketing budgets if not speaking anything else. I do not see any way I could defeat them.
      So I now just build a new app with very small steps, trying not to exceed my time budget, and not spending at it anything. The goal is small, just to overcome the hindering problems of my existing app, which is a mix of open source and my closed code.

  20. 2

    The way I like to think about it... Every time you build an app and publish it you're getting better at your craft. These skills are sometimes worth more than money.

    Even the most prolific indie hackers like Peiter Levels admit that most of their projects don't make money. But they recognize the value of continually creating.

    Of course, the danger is that you spend years building something and still don't put it on the App Store. Stay focused on the goal, try to reduce the scope and publish an MVP. It will be much more satisfying to see if their are other people download the app than it will be if you just build it in private.

  21. 2

    I did build the app for my personal use and put it on the play store for fun. And I'm not expecting the installs. But surprisingly I got 10K install and also monetize for 3 Months. Later admob suspended my account saying some policy violations.

  22. 2

    Often the best ideas are born when you're trying to solve your own problems. You don't expect much of it, so you don't focus on buzzword techniques for growing a business. Instead, you focus on creating the best solution possible.

    I love how you explained why you're building it, and why you don't like other apps that do the same things.

    When you're promoting the app, focus only on those things!

    People who would want it are already aware of mainstream apps like this. If they look further, it means they don't like them.

    And it's probably one of the things you mentioned.

    By explaining your problem with other apps and the solution you created, those people will recognize themselves. They will eagerly download and use your app.

    Do you think nobody else feels the same frustrations as you? Still think it's pointless to build it?

    Good luck with your journey!

  23. 2

    Somehow the probability that somebody as the same problems is very enormous. Go for it 💪🏾💪🏾💪🏾

  24. 1

    i understand your frustration with existing wellness trackers. Building an app that meets your specific needs can be incredibly fulfilling, even if it doesn't generate much revenue. Your app could resonate with others facing similar challenges. Don't worry about building something for one person - your experiences may represent a larger audience. Share your journey on your blog and inspire others. If you need help along the way, check out ValidatorAI (https://validatorai.com/) and Checkmyidea-IA (https://www.checkmyidea-ia.com/), AI tools that streamline validation. Follow your passion, build that app, and enjoy the process. Good luck!

  25. 1

    I'm a fresh college grad aiming to learn most of the skills needed to a basic indie product from scratch. I don't quite know where to start yet,, or what to focus on, or whether my idea makes sense for anyone except me, but the discourse under your post has been eye opening Alex!

  26. 1

    I have built two apps that I wanted, hoping that others would want it too. It was a great learning experience. Now I can build an MVP (react-native) in a few days and test it by myself or others.

    But I couldn't grow the app beyond a hundred users. Why? because it wasn't something that I really wanted (when I was building it I thought I wanted it). It was something that I would build if I was forced to do a school project. Something that makes sense in my head but in reality not needed. It took me a few months of coding to find the reality out.

    So if you are looking beyond learning and hoping others would use the app, I'll first talk to people who might be interested in what you are building.

  27. 1

    Nice concept, building app for oneself. May be you are putting a thought on creating Micro app which has the capacity to know more about your preferences.

    Who knows in few yers, there may be there will be app for each individual, where the brands will come and integrate with you..

    Super concept. I liked. it.

    All the best Alex.

  28. 1

    Yes. I built two for myself:

    I'm obsessed with superfoods and getting daily nutrition through food: Built https://recmend.com

    I needed a simple tool that I can collect and save links and make them searchable: Built https://linklist.io

    1. 1

      hey! i quite like linklist!

  29. 1

    Go for it. But try to sell it anyway. Get feedback early on for sure.

    There are probably others who want a health app that is private. You won't be the only one.

    I advise you try and build it so it's easily useable and easy to understand. You can still make it highly customisable and personal to your goals, but this should be done with a lot of thought into the UX so it feels natural and there isn't a steep learning curve.

    This way, it won't just be for you and others may want it and worst case scenario, even if it is just for you, you have learned a lot about creating a nice UX.

  30. 1

    If you insist on a high standard to entertain and fulfill needs for yourself, I think you are on track to build a great product. The only thing I would ask myself if I were in a similar situation might be would a beta version be enough for a market test rather than building every possible feature I could think of.

  31. 1

    Many applications were first designed for oneself, and if we have this problem, it means that others have the same problem.

  32. 1

    if it helps you, then why not ?

  33. 1

    Hey, you can create a app for yourself but it is based on your opinion.

  34. 1

    def keep building it because if you make something that you love for sure it is going to help and impact other individuals.

  35. 1

    Echoing others why not? Just be reasonable in your expectations. On the upside, If you're your audience, only polish it to the point that you'll actually care.

    Unironically, a friend (seriously, not me) did this building Habit100 and ended up getting a couple people emailing him thanking him for it. Which is pretty great for an app that hasn't been marketed. https://apps.apple.com/us/app/habit-100/id1577102319.

  36. 1

    If it is something you would use and see a need for, I expect others will too!

  37. 1

    I also prepare my projects completely according to my needs, in fact, something we need may be needed by others.

  38. 1

    I think as a developer if I can create something to simplify things for myself, then the answer is always for me is - Why not!

  39. 1

    I'm actually doing something similar for me, even thought it will be a website.

    • You will learn or improve your current dev skills (I'm a dev and it's never enough, we can always learn something new :D)
    • It will be tailored exactly to your needs, like nothing else
    • You can still show it to other people, and you will get feedback that can make that app even more useful for you
    • A lot of soft skills involved, nmw, even if you aren't a developer. Problem solving, UI design, product design, etc.
    • The market may be saturated.... but who knows what will happen ;)
  40. 1

    Hi Alex,

    I'm trying the same, also in saturated area :)
    One thing, there's a typo in your blog url :)

  41. 1

    More people need to build for themselves.

    If you think about an enterprise or growing business, they make tools to allow their process to be less friction. As a single person, you can gain more from this then they can...

    Look at yourself as a cyborg (we kinda are nowadays...). You can let someone else you don't know write your personal OS or you can write your own and be who you choose to be vs what others decided.

    This is my mentality when making software for myself. And I make a ton for super specific reasons, and you can cut as many corners as you need and keep it raw to satisfy what you need.

    I can write a small book on this topic after doing it for so many years, around if you want stories!

  42. 1

    Go for it! You are on the right track

  43. 1

    I think its good, and if you have this problem then maybe some other people do too. Its just that you dont know how to find them or who they are yet

  44. 1

    Absolutely, I see it for 2 reasons

    1. You're building something that's solving a true problem. If you're having that problem that more likely that not, someone else is

    2. You're continuing to hone your skills. Even if this becomes a project that only you will use, you're honing skills that will pay dividends in the future

  45. 1

    As long as it's useful to you then yes. I have built myself a flash card app (to learn a language) simply because it was very easy to build and I did not want to pay a subscription monthly for such a simple thing

  46. 1

    I'd say go for it! It depends on how complex the concept is, and what the effort/reward curve looks like for the development process, but in general it sounds like it'll solve a real problem.

    I created a small time-tracking app for myself; the first version of this was literally a PostgreSQL table into which I manually inserted entries! Eventually I threw a slim UI on top of it, but despite still being very simple/ugly it meets my needs. For personal projects I like to be aggressive about the "M" of "MVP" -- as a personal project it can even be a little buggy, since you're the developer and know how to work around the bugs.

  47. 1

    Yup. I've built all sorts of stuff. Just keep talking about it and sharing it and you might uncover a great need! Good Luck!

  48. 1

    I think it definitely is! I say go for it! I have built a couple of things that I thought would be useful to only me and they have gone a long way to help my work flow. Good luck!

  49. 1

    I think you answered your own question. "the level of delight it would bring me to create the product that is missing from my life might just validate the whole endeavour."
    Be Bold. The Mighty Forces Will Come to Your Aid. - jj

  50. 1

    you should be building an app which solves your problems and people like you mostly internet based startups had a profitable app idea

  51. 1

    You need some strong validation, here are some free tools for you to help in this situation - https://unicamel.io/checklist-kit/

  52. 1

    God bless people like you!

    I'm doing the same for the last two years. I didn't even validate the market and if it's needed for anyone.
    What motivates me is that I'm building a tool that I will use on daily basis myself (once it's built and working).
    While working with startups I taught a lot from them, and main thing I learned was: "first, you need to solve problem for a single person, and later look at bigger picture"

  53. 1

    Great tale! Good part of it is when you fixing you difficulties, you will achive the greatest outcomes and can develop a wonderful product, but there is other side, did this product is actually required for other people? I think the best option is to create services based services or sell for the people checklist or any other digital product, to validate did they really want to spend money on that, only than you can understand what can be your expectation in the market and also you collect some audience, which can answer your questions!

  54. 1

    I'm doing exactly that for the past few months, and it feels great! It started with my own frustration about a problem I had.

    I knew it could be better, and I went on and started building a site to solve my own problem. The creative energy being poured on this hobby project feels just great, even if it's just for me. Turns out a few friends wanted this as well, so they started using it as well.

    I'd say just go for it, until it stops being fun and starts feeling like a chore.

  55. 1

    Hi man, its not pointless, I assume youre a programmer so building anything will make you a better programmer, secondly if this app solvesa problem you have im sure that other people needs the solution so making money out of it is realistic with the right business model. I wish you good luck bro 😁

  56. 1

    Obviously, if you are happy to just build it for you: do it ;)

    Then again, if you have checked all the apps out there and your particular need is not met, chances are there are more people like you out there. From what I read here, it would be health and data privacy conscious users.

    So if you need a little extra nudge, try to find those people online - for example in facebook groups and engage with them. See if they also have this need.

    Monetization should be fairly simple - as far as b2c apps go - with a freemium model. Since there is an ongoing, continuous use subscriptions should work fine.

  57. 1

    Yes build it! Or talk about it here? You will get early validation on the idea if you are being transparent.

  58. 1

    If you are frustrated so are other people so don't write it off as not a business yet! IF it makes you happy then it is worth spending time on. Once you have it you can see about making it into a business.

    Oxogen.io is launching to help founders with just this sort of thing BTW

  59. 1

    EfficientNetHack on Gmal d0t com was really good to work with. They were helpful and patient in answering all my questions and making sure I understood the process. Sign up was very easy and for once I feel positive about my future credit as I know I am in good hands. They seem to really know their stuff and I finally feel I am on the path to repairing my credit. Thumbs up guys

  60. 1

    Not a bad idea! I like the idea of building your own app for a personal purpose. First and foremost, all apps should be used by the team behind them. You can actually validate your app if you are interested enough to use it yourself. That's where success begins! Good luck! If you are exploring open source platforms to build your mobile app, I recommend visiting https://catalyst.zoho.com/build-serverless-mobile-applications.html?src=footer - the reason I suggest is that the build environment is completely free. (A late comment to your post, any which ways if you are still planning to build apps this might be relevant)

  61. 1

    There is one thing I can say for sure. If this app is solving this crucial problem for you, then for sure it is the same for several others. I can see that you've figured out what problem you really want to solve so badly, then that is just why many others would want to use this solution for you.

    Therefore, go for it!

  62. 1

    I've had a similar thought about "todo" apps. There's hundreds of them... but none of them work in a way that work just right for ME. My work style can't be THAT unique... maybe it's worth building even if it's just for me and if it works for others, even better.

    1. 1

      I also have the problem, always struggling whether to build the apps or not...

  63. 1

    I think more people start this way. There is no 1 perfect way of building what is to be a "successful company" (whatever the metric for success for each individual is). You can't pick winners, no matter how good we plan or ideate. I've been building brands, products, and apps for people for myself and clients for a while now, and it's just a fact. A winner is built, iterated, tested, and all of that in a continuous cycle.

    That said, you can just look at this phase as your ideation/validation phase. I don't see anything wrong with that. Especially if it's financially not damaging to you, why not?

    After it being built, will it actually solve the need you were trying to meet? Does it need itteration? And these questions you have to be utterly critical about when answering as your a testing audiance of 1.

    You pretty much take a different direction and at some point will probably try to find a market fit for your product (as opposed to some who start with a defined market and build products for them).

    I think both can work.

    What would be even sweeter (my personal strategy) is that you building this app can actually aid your main revenue-driving business (whether it be; a case study, portfolio piece, consulting work,...) this way you can use this project and package it as a productized piece (sell your sawdust to some extend).

    Hope it helps a bit.

    Sai

  64. 1

    Alex, I'm having the exact same struggle as you. Literally. I've been so disappointed with every fitness app, that I want to build my own. I also have low/no expectations of it, but I think it would be great for myself, and will help me learn by going through the planning & building process.

    Even in a crowded space, I can guarantee you aren't the only one who hates the current options. I know that I'm responding a year and a half after you posted this, but I think you need to go for it!

  65. 1

    Love this post! I would definitely build it if I were you. It's worth creating the app if it enriches your life. It doesn't have to generate any revenue.

    I also think that building the app for your personal needs without caring about the profitability might help innovate the health/wellness trackers. You may not be interested in making the app available to others now but there have been a lot of cases where people's hobbies turned into a successful business later and revolutionized the whole industry.

    Exciting project! Please keep us updated:)

  66. 1

    I would say if you have the time, money, and energy to expend, then go for it because if you experience this, then you are not alone, which means you can build a niche market for yourself and if you work hard enough at it, make a great living for yourself. Sure, it's not gonna make you Bezo's rich, but who cares if you can make a living doing what you love and even retire early with a great life!

    But, it really just boils down to how much time, money, and energy you're willing to dedicate to this because no matter what...It's a lot of work.

  67. 1

    Same question!! I have had a Vikings clothing product store running for 2 years my ROI has been reached 30%. Would it be a good idea if I create my brand app for growth? This store has Viking jewelry, armors, and clothes https://vikingclothing.net/. please help...

  68. 1

    You should do that. I built a small browser extension to manage clipboard history just for myself in 2014. I had no expectations since clipboard managers is a pretty staffed market.
    I never invested in marketing, but the extension has 100,000+ users right now. Turned out I wasn't alone who needed such a thing.

  69. 1

    Hey! If your app solves your problem, there is a chance it can solve problems for others too. Did you get a chance to work on your idea?

  70. 1

    I did exactly this with www.everyhour.xyz and learnt so much and gained so much confidence doing it.

    Also I just looked at your personal site and your portfolio is amazing!

  71. 1

    Ya i'm on the same bus and i think if its your first real project then better to build it and learn than keep waiting for some world changing idea... i'm building https://www.indiehackers.com/product/teamlink for myself and my tech teams and would be happy to collaborate/give-feedback to others in same boat.

  72. 1

    Definitely!

    Worst case you learn how to build an app.
    Best case, others also need it and you have a potential business!

  73. 1

    I am all about building -- and really polishing -- my personal tools, even if they're never seen by anyone else. Spending a week or two building out a new tool or connecting a feature in an existing one is pretty much always time well spent: the worst case is that I end up with a new superpower (hello, automatic cloud orchestration tooling).

    And in the best case I end up with a standalone, interesting, pre-validated product like the revenue forecaster I use to look at growth metrics from the future 🚀!

  74. 1

    Hi Alexandra,

    Absolutely. First, you'll learn a lot. Second, you might find others could use it.

    I created one for myself as well - it adds an option into the Share menu on my android, so I can post the URL to airtable, where I'm building up a list of a certain type of tool online. It saves bookmarking it and trying to add it manually. It took me a few hours to write (I guess around 7-8), but it saves me maybe 2-3 minutes every time I use it, which mounts up over time.

    Plus it just feels great to do something in 1/4 the number of clicks it normally takes :-)

    Andy

  75. 1

    Could you please send more details ( what functionality would you like to have etc.) concerning your future app?

  76. 1

    Good luck, you may find others that have similar needs.

  77. 1

    Hi Alexandra! If you have a strict budget you need to test market demand for your product. The best way to do it - launch an MVP of your project. It saves you a lot of money in the future and helps to identify the "pains" of your future customers. For more detailed information you could read this article https://linkupst.com/blog/what-is-the-discovery-phase-and-why-is-it-necessary

  78. 1

    Build it and share it here so I can check it out (and very possibly use it haha)!

  79. 1

    Many successful ventures started as "pointless" ideas - good on you for giving it a go! How have progressed so far?

  80. 1

    I'm in the same boat. I want to build a "media archive journal" app for myself and I've been struggling with whether it's a worthwhile use of my time to build it or not. Although I haven't opened Glide in almost a month, I actually have a session with my Glide mentor tonight.

    I hope you build the app. I say go for it!

  81. 1

    Privacy matters more and more. If you store the data in NoSql or storage method on the users device, people would pay for it rather than get it for "free" and the user be the "product". I've been watching this trend for the past year now of decentralized apps, especially in certain segments where privacy matters the most. Health/wellness seems like a perfect place to implement this.

  82. 1

    Yes! I'm building Hitsnag, which shoots what you email yourself straight to the productivity app it needs to be in. I email myself all the time and usually its the problems you encounter the most that cause one to create a useful solution for many. You should def ask around for some validation and make sure the cost stays low.

    Hitsnag's waitlist 🙏
    https://www.producthunt.com/upcoming/hitsnag/

  83. 1

    This comment was deleted a year ago.

  84. 1

    This comment was deleted 2 years ago.

  85. 1

    This comment was deleted 3 years ago.

Trending on Indie Hackers
How I grew a side project to 100k Unique Visitors in 7 days with 0 audience 49 comments Competing with Product Hunt: a month later 33 comments Why do you hate marketing? 29 comments My Top 20 Free Tools That I Use Everyday as an Indie Hacker 16 comments $15k revenues in <4 months as a solopreneur 14 comments Use Your Product 13 comments