Hacker News new | past | comments | ask | show | jobs | submit login

Why would you need to quit your job to make a meditation app? Can't you make one in a few days? They don't have any social elements etc, just an app that plays music and notifications.



> Can't you make one in a few days?

Here we go again :-).

Now a days I've become a big proponent of "Talk is cheap, show me the code", not just in s/w field but in general.

If someone says "I did it in 3 days and here is how I went about it" that will lend them more authority and also lead to all kinds of interesting conversations and learnings.

Mind you, I used to make similar comments but over the years as I introspected I realised there's not much to be learnt by building castles in the air and talking about it from the sidelines.

As they say, in theory there is no difference between theory and practice but in practice there is.

Edit: More content.



This is not the same thing though.

The Dropbox trope is "we don't need this product, because the end-user could built it themselves using tech tools"

The comment you replied to is "why quit your job, build an MVP"


Well, first of all, his intention was to quit their job in the first place, with app or not. The app was created to support the quiting, not vice versa.


An obvious difference is that Dropbox was very early in its niche while at this point we already have many great meditation apps.


this is my favorite response to something like this


The original author of that comment is still active and reflects on it from time to time when it pops up.


If you trying to build a business there is a lot more to it than simply building a prototype. The problem with the MVP/prototype idea is that it cheats people into thinking that there is some sort of straight line between idea, prototype and success.

There isn't. There is maybe a hundred iterations between idea, prototype, marketing before something catches traction. And that is where persistance, focus and dedication (including quitting your day job) comes in.


and turn off and back on notifications and calls. and dim the screen. and collect the progres. and allow for intermediate "checkpoint" dings . and are flexibly configurable. and allow for guided meditations. definitively minimize power consumption.

etcetcetc

ps: for a backend think about collecting meditation statistics, and pulling in meditator networking, online meditation groups, running longitudinal meditation studies "how was your sit" and other parameters... if you eont put that into the meditation app you want the meditation app to send notifications to the other apps, so add events and notifications to the no-backend list above.

point being: its more than a timer and notifications.


Not to mention, a double-blind questionairre following a meditation, meditator ELO score and finally match-making based on said score.


how could I forget about the meditator ELO score! competitive meditation! rankings!

you made my day :-)


You could make something in a few days but probably nothing that you would be proud to show the world. I wouldn't be surprised if OP spends a few days just playing with colors and fonts to find something that looks great.


OP never said they needed to quit to make it, they wanted to do they did and now travels the world.

Which is pretty awesome.


You could write Facebook in a couple days too.

How long does it take you to develop an edge against your competition?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: