Great job. Lots of lifting tracking apps out there, but kind of wonder legality around naming apps around popular systems. Not sure if Wendler has trade mark on 531 or even official app. I think there was some drama over Sheiko app when it was released, but he's Russian so maybe too much jurisdictional PIA to resolve. That said, it does feel kind of not right there's so many 531/SS/StrongLifts apps out there brazenly using the routine name for their app.
Tell HN: I made $1000 with my app and now making $500/mo
161–170 of 186 posts
Re: Tell HN: I made $1000 with my app and now making $500/mo
#162Earlier quoted context omitted.
Personally I use FitNotes to track my workouts (5/3/1 or not) and keep (the totally not responsive) http://lift.eha-ab.ca/ open in my mobile browser.
Don't know if you have, but you should check out my online calculator then. https://fivethreeone.app/calculator Let me know if there's anything you'd like to see in there.
Neat, I'll try it!
Personal opinion:
A toggle to have the program at the top would be handy. Also I don't really need the plate details for each set.
The program is not totally responsive.
As someone who does a very basic 5/3/1 I was a bit lost with all the variations, it's very complete!
Re: Tell HN: I made $1000 with my app and now making $500/mo
#163$500/mth is $6,000/yr At a 4% safe withdrawal rate what you've built is the equivilent of saving $150,000. You should be EXTREMELY proud of yourself, and never underestimate the power and value of the asset you've built
Why it's 4% a safe withdrawal rate? Is it safe in the current economic context? Isn't affected by inflation?
Taking out 4% is usually considered the safe bet on keeping the original money at the same value year after year with the remaining excess returns accounting for inflation.
Even if that amount is too much for 2022 and 2023 due to higher inflation, during other years, it will be too conservative. So it evens out. Plus there’s recessions too. So the 4% is an average.
Re: Tell HN: I made $1000 with my app and now making $500/mo
#164Earlier quoted context omitted.
> If your code is incorrect and disorganized but readable, it will be hard to fix and extend, but easy to refactor, thus more extensible and fixable. The state you want to reach is "fixed", not merely "fixable". I've seen too many people applying your reasoning staying perpetually stuck in the broken-but-"fixable" state because they prioritize "readability" higher, and I'm saying your users don't care about that. The…
> The state you want to reach is "fixed", not merely "fixable". And my argument is that readable code is the most direct route to that state. > > And code is always incorrect. > This makes a strawman of my argument. It would if it was actually part of my argument, and not a cheeky parting shot. Here's the straightforward version. In my experience, the most productive way to approach code is to assume that at some poi…
> And my argument is that readable code is the most direct route to that state.
Which has absolutely nothing to do with my point.
Nobody is arguing whether you should keep your codebase readable. The question is whether that should be prioritized over correctness.
The situation is: your codebase is already as readable as possible, but you've now discovered a problem for which you're failing to come up with a readable solutions. [1] I'm saying, when that happens, you need to be willing to just bite the darn bullet and go with the ugly-but-correct solution so that your customers actually get their problems addressed. Don't just leave it as a dangling "known issue" or leave some silly hack in there just to "keep the code readable". Your customers/users won't applaud you for keeping your buggy codebase readable. Of course you can feel free to make a ticket or leave a TODO in case you're hitting a blind spot or someone better comes along in the future. But for now, solve the dang problem first, because your customer isn't paying you for source code, but for the end product. (Well, unless your customer is paying you to ship source code to them, in which case you should ignore me.)
[1] To be crystal clear (and hopefully avoid more strawmen...), I'm saying you (and your team/company/etc. as applicable) need to actually do your best to implement a readable solution first, and THEN fall back to an unreadable one if you fail to do that despite your bona-fide attempts. For some reason (maybe it makes it easier to argue over the internet? maybe it's just more convenient?) people love to strawman "you should prioritize correctness over readability" as "you should go with the first solution you like whether or not it's ugly; feel free to leave a TODO for some poor soul to polish it later". Which has emphatically never been what I've been saying, but that's what people appear to respond to.
Re: Tell HN: I made $1000 with my app and now making $500/mo
#165Well done! $500/mo, though not crazy money, is significant. How did you market your app and how long did it take you to build out the app? I've built an app as well while I was doing my regular day job and recently quit the day job, mostly due to being burned out working in big tech as well. During my break from work, I decided to try to get my app sales up, but it's challenging. (During my best month, I think I got…
Thank you! I feel you 100% when you say that keeping user happy is incredibly gratifying. The app took me about 300-400 hours to build. Regarding marketing, I've said it elsewhere in the thread but here it is again: - Created an instagram account for the app and started following some tags. I liked post on the tags and started following some users to get them to look at my profile. Got about 150 downloads from that.…
One thing you should know is this. Never advertise through Instagram and their ad platform. Instead, use the Facebook ad platform which will more effectively advertise on Instagram as well (if you even want to advertise).
Re: Tell HN: I made $1000 with my app and now making $500/mo
#166Earlier quoted context omitted.
> The state you want to reach is "fixed", not merely "fixable". And my argument is that readable code is the most direct route to that state. > > And code is always incorrect. > This makes a strawman of my argument. It would if it was actually part of my argument, and not a cheeky parting shot. Here's the straightforward version. In my experience, the most productive way to approach code is to assume that at some poi…
> And my argument is that readable code is the most direct route to that state. Which has absolutely nothing to do with my point. Nobody is arguing whether you should keep your codebase readable. The question is whether that should be prioritized over correctness . The situation is: your codebase is already as readable as possible , but you've now discovered a problem for which you're failing to come up with a readab…
It feels like your argument is a bit of a strawman itself. I'm hard-pressed to come up with a situation where the code is broken but readable, and the quickest way to fix it is to make it less so.
Sure, there are times when I don't know or don't have the time to come up with the best structured solution, but have to put something out there that just works. I would argue that's where you should strive to make it even more readable, because the uncertainty means the odds of having to revisit it later are even greater.
Re: Tell HN: I made $1000 with my app and now making $500/mo
#167Good job! I know exactly the feeling. I'll once again shamelessly plug my project, since it's vaguely relevant. I'm making about 200 USD/month by selling watermark removals on https://gifmemes.io . What I've learnt is that I'm very bad at marketing & design and will much rather spend hours programming useless features. For example I've spent like 10 hours getting an wasm ffmpeg converter of gifs to mp4s and webms, wh…
For what it's worth, I'm the kind of person that would pay full price if I saw and clicked the "It's too expensive" button :)
Re: Tell HN: I made $1000 with my app and now making $500/mo
#168Thank you for sharing! I wish more people were transparent about money (to know what's possible). In my example, I created Video Hub App that sells for $5 (and $3.50 goes to a cost-effective charity). I'm averaging about $500 for over a year now (with almost $15,000 donated to charity). https://videohubapp.com/ & https://github.com/whyboris/Video-Hub-App (MIT open source)
Wow this is cool. How long did it take to build it?
About 4 months for the version 1.0.0 - all outside of a full time job (I was really excited and spent maybe 20-30 hours per week on it maybe). Since then it's been about 3 years of intermittent work - adding features, fixing bugs.
The announcement post on HN: https://news.ycombinator.com/item?id=17587992
Re: Tell HN: I made $1000 with my app and now making $500/mo
#169That's amazing and inspiring.
I had thought about making a 5/3/1 app when I got into powerlifting but thought to myself "nah, no one would pay for it and there're so many apps out there already". The inspiration here is that I need to validate my assumptions or really be skeptical about them.
Congrats!
Re: Tell HN: I made $1000 with my app and now making $500/mo
#170Congrats! At 4% yield, that's like you've made (and invested) $150k, after tax. Before tax that'd be a yearly salary of well over $200k. If you can do 2 of those every year, you're on par with mid-level FAANG comp, once you include RSUs. There's probably a benefits and self-employment tax angle I'm leaving out though. And surely it's more volatile. But if you can keep it up it seems pretty solid.
While I like the thinking, it's not quite the same as an index returning some yield is far more likely to give returns indefinitely, whereas an app can become obsolete.