12 ms·
The saddest "Just Ship It" story ever (2020)
- tdeck 2y agoA few years ago I built a payment system for Google Forms as a side business (made about $3k from it before eventually turning it off to focus on other things). I'd found a problem nobody was actually solving and wanted to see if they'd be willing to pay to solve it. Like many of us I also had a bunch of partly finished projects that were never released, so I knew it could be a struggle to ship things. What I ended up doing was writing a list of all the features that I wasn't going to work on, and all the compromises I was going to make to get something out there. Some of those compromises really hurt when I was writing them down, but didn't end up mattering enough to change them for over a year. Once I had them on the list, it gave me permission not to thing about them while I implemented the rest. I also staged the development to avoid anything unnecessary if it flopped. For revenue, the idea was that I'd get a card on file from you, then bill it each month. But I launched the thing with no integration at all for the card on file. My plan was to give people a 14 day free trial, and if anyone actually used it in that time I'd use the time to build a card acceptance flow using Square (their API is like Stripe's). It turns out people did find and use it, and I had to extend the trial a bit, but eventually built the form. Then I had until the first of the next month to build the system to total up their bill (based on usage) and charge the card on file using the rest of Square's API. I also didn't build anything at all for scheduling account lifecycle events. I used varmail.me (a little thing I wrote forever ago) to have my app email me when someone signed up, and check my inbox a couple times daily and send a canned welcome message to any new users. Then I'd write an email reminding me user X's trial expired, set myself as the recipient, and use Gmail scheduled messages to schedule it 14 days in the future. When I got that email I'd check if they're still using the product, send them a reminder to put in their card on file, and manually mark their account as inactive until they enter a form of payment. Billing jobs were run manually by me on my laptop for a while. Over time I got more users and it was worth the effort to replace these manual processes with automated ones. If nobody had used my product, it wouldn't have been worth the effort to automate any of this. Testing was another thing I experimented with doing differently. At first I tested everything manually. Automating tests was difficult anyway because the key flow redirects through PayPal, and there were parts written in Google Apps Script. Eventually I built an end-to-end selenium test. Then I started adding unit tests where appropriate. Basically my principle was that I added automated tests to any area where I felt uneasy about making changes for fear of breaking something. Since I'm fairly risk-averse, the product was small, and I worked on it solo, this worked well for me.
- f3b5 2y agoThanks for sharing! I'm going through the same thing at the moment, and it's nice to read that this pragmatic approach has worked well for you
- schobi 2y agoIt sucks to realize that someone else beat you to a proper release. Happened in my last job, we went though the stages of grief just as the author here. In the end you learned a lot about new technology, about your pace of development, about you thinking, about aspects you like and don't like. The lessons learned "ship it" prepares for next time.
- lukan 2y agoOn the other hand, there is no second try, to make a first impression. And the first impression lasts a while. So at least get some feedback before "just shipping". Otherwise reactions might be "doesn't work" - because what was obviously a start button for you making it, was not so obvious for someone just stumbling over it.
- tass 2y agoIt doesn’t need to be shipped to the public. He shared videos with people, and those same people can be the first users of the MVP. The point of an MVP is to elicit feedback, know you’re on the right track to build something useful, and iterate.
- lukan 2y ago"It doesn’t need to be shipped to the public" Ok, I took it by the usual meaning of ship it to the market. Not having people test it.
- com 2y agoI think also, it’s not just “people”, but “people that you hypothesise have a problem that you’re aiming to solve”, and perhaps even “… and have money that they can and want to spend on solving it”
- jascha_eng 2y agoI wholeheartedly agree with this, when I started working on Kviklet we were a team of 3 and one of us was a lot more perfectionist than the others. It took a lot of convincing to even put our (tbf shitty) first website version up. Much more to release our repo. We lost that "co-founder" early on, but man I'm glad we released early and tried to sell. It didn't work and we found no buyers but imagine we still were working on a product without knowing if anyone would ever want to pay for it, keeping our hopes up in the dark. By now we went with the backup plan and open sourced and have a few cool users. Could maybe even say it's a small community: https://github.com/kviklet/kviklet https://github.com/kviklet/kviklet It's not the startup success story that I hoped for a year ago. But it's a lot better than still hoping for it and not being a bit more grounded. Also open-source doesn't mean I can never sell support or a premium version and still make a few bucks right? For now it's just a fun side project though.
- 38 2y ago> Pull Request-like Review/Approval flow for database queries Terrible description IMO. a query should not need approval. Should use mutation or edit or update or modification. Even if query is technically correct it just sounds wrong and confusing.
- loa_in_ 2y agoYou say it's confusing, but it's exactly what I expected it to be based on the description
- jascha_eng 2y agoI'm not quite sure what you mean. Maybe statement instead of query would be more accurate but I think people get the gist of it just fine. Also, I disagree a manual query like: "select * from credit_cards;" should probably go through an approval flow if you have a table like that in your prod env.
- jamesfinlayson 2y agoA guy I used to work with said he worked for a company where all queries had to get approved by one of two full time DBAs - apparently with good reason as someone tried to modify a query that would have joined with half the rows in some gigantic table.
- firefoxd 2y agoI started mine in 2017, after I left the start up i co-founded. 2 months later, the app was. I still haven't posted a show hn. In fact, after 2 years, someone approached me saying he is building the exact same product, but in Germany. We had several zoom calls. He shipped it, failed and iterated. I'm just watching him and hoping someday I get some time to actually do something with mine.
- ggeorgovassilis 2y ago> so I started getting suspicious if someone actually shared the video of my app with these people because they were solving literally the same problem I once met a guy who had a good idea about an app, something that became fairly mainstream two years later. He asked me to code the app for free and we'd share revenues. When asked what his contribution would be, he offered to "run" the company and otherwise his 50% was "having the idea". I thanked him and told him that he has a head-start of 6 months, if his app hasn't hit the market by then, I'd write the thing myself.
- deadbabe 2y agoNot sure if it’s smart to do that if you aren’t entirely sure about what mental state a person could be in. Edit: okay I don’t know why I’m getting downvoted for this but if you think you can just tell someone you’re going to steal their awesome idea in 6 months you better hope their not the type of “crazy” entrepreneur who will cause problems for you or in extreme cases even end up shooting you in the back of the head.
- ggeorgovassilis 2y ago> okay I don’t know why I’m getting downvoted Because saying "don't do something because an irrational player might irrationally punish you for that" isn't particularly insightful. To expand on your argument, I could find out your real identity (this is hacker news, so I might be a hacker) and pay you a visit (I won't, I'm too lazy & incompetent for that). Just saying that your argument doesn't make sense to me. > you’re going to steal their awesome idea I paid for it by listening to a bad sales pitch, that's 40 minutes of my life I'm never getting back. Also, there was no confidentiality or non-compete agreement. > end up shooting you in the back of the head Only a semi-related tangent, I live in Europe, people here usually don't carry guns which shifts the entire risk/reward calculation significantly.
- deleted 2y ago[deleted]
- 2y ago
- 999900000999 2y agoDepends on your target audience. I have a side project that's just an internal tool for my music visualizer/ lyric video generator. It has no functional sign up for new users and is very difficult to use. It's "shipped" as in I use it for my projects. Another is a simple web app a friend requested. He uses it occasionally. I'm sure y'all on HN could probably find half a dozen issues with it. But it's what my friend wanted and I learned a lot. The moral of the story is use Flutter from the start, don't worry about shipping apps( do you really want to struggle with the various app stores for what's just a web app anyway), and ship early and often.
- adastra22 2y agoWhy not ship now? Well not now in 2024, but when this article was written? Most apps and services you use were not first to market.
- victorstanciu 2y ago> Even though they were working on it for the past few years it's still slow, buggy, and super unpolished, it doesn't matter, because they shipped. > Their mobile app is terrible and it needs 10 seconds to sync. It doesn't matter, they shipped. And I'm looking forward to every single update they release. > Their backlog of things to do is huge, but it doesn't matter, they ship every single week, and the app is growing along with the community. Sigh. I agree, and I can empathize, but as a user I am so sick and tired of half-finished crap being shoved out the door just to beat the competition to the starting line. Every day the software we use becomes slower, more bloated, and less stable, and part of it is exactly this attitude of throwing crap at the wall and hoping it sticks. And the sad part is, since everyone is doing it, you can't really not do it, otherwise--as the author discovered--you get left in the dust.
- tithe 2y agoI've always thought that hanging a "beta" on a logo isn't an excuse to ship junk, but as you allude to, sometimes product and service quality isn't the priority. I'm also reminded of Dave McClure's talk [0]: "Don't do your viral marketing campaign until your product doesn't suck! Because what will happen is people will tell other people that your product sucks! ...So don't do that!" [0] https://www.youtube.com/watch?v=irjgfW0BIrw https://www.youtube.com/watch?v=irjgfW0BIrw
- ajaymenon0 2y agoYeah I so agree. Specially post the AI boom, there's just this intrinsic itch I see of taking a product that queries chatGPT and slaps an AI label on it to make it a product. (I'm look at you Rabbit R1). I do understand that it does foster some air of competition and hence there's a the capitalistic push of doing better than the other person. But then, a lot of sub standard software leaks through which shifts the whole benchmark for acceptable user experience.
- theideaofcoffee 2y agoI feel this deep in my bones. I worked on <some project> a long while back because I wanted to scratch an itch, and I thought that some of the problems I was seeing, hey, maybe someone else was having them too. So I start kinda-sorta-half-heartedly exploring the idea, writing some pilot code, then I discovered hacker news. And oh boy did people have things to say about the general problem, it's impossible to solve, no one should waste their time, we can just <do the drop box thing and wire up ninety five things and make it shamble along>, definitely no need to waste time trying to implement something new from scratch. Then I dropped it, because, hey, the glitterati of hacker news and all of the others must be right, huh? I let it wither, while working on other things, working for other people, making them wealthier, while all in the back of my mind I keep thinking: "maybe I should keep working on it." Services doing the same exact thing started popping up. They get traction. Users are mostly happy with what they were doing, but they didn't have half of the features that I had already implemented in the code that hadn't seen any use outside of my testing environment. Some take off so well they have a now-publicly traded company doing the same thing. Ten years after I started my little project. Fuck. Lesson learned. The naivete of youth is a harsh teacher. Work on it. Put more effort into it. Ship it. Go with your gut--you probably have a better sense than you think you do of what will work and what won't. Ignore the hivemind. Don't leave room for the regret you will inevitably feel when you're scooped.
- zogrodea 2y agoI'm sorry that happened to you. The comments here are generally high quality and I've learned quite a lot from them, but there are things I've learned from experience that go against conventional wisdom here. Although not as drastic a case as yours, I think it's often worth being critical of what one reads here and keeping one's ideals until actual experience makes one incline one way or the other.
- worthless-trash 2y agoI would say if you take hacker news advice about what works, you're a bit of a fool. HN readers are in the pool of people who would be your competition.
- Culonavirus 2y agoThere's massive caveat with all of these "and then the story ends because we didn't just ship it :(" stories: sometimes the value of the "app" you're working on is in the technical details that cannot really be "hastened" and you can't "just ship it". Also, and this is something a lot of the managerial class people don't want to hear: Your job as a sw engineer/architect is to resist the "just ship it" pressure from the management as much as possible. So unless you own what you're coding and you really need it out of the door for your own benefit, if more time makes your work more professional, then take more time. Anyone telling you otherwise is a 100% hack. You are not an automaton that takes in JIRA tickets and spits out hacky code as soon as possible. Or at least you shouldn't be. Not to mention that not taking time (doing things properly) is incredibly taxing on your psyche and you WILL burn out. There are only so much garbage tasks you can take. It's worth repeating: Unless you have a stake in the company, it is NOT your job to make sure the company is the most profitable it can be. Your job is to create great software. What's great software? The kind you'd be willing to put on your resume without feeling bad. This is the thing that will ultimately make you feel good about the work you're doing. Hitting that arbitrary deadline for a 1425474th time may feel like a relief but it's short term and a form of negative motivation - and in the workplace, those NEVER work over a long period of time. So RESIST that pressure from the top and do your work properly. If they fire you, then who cares, the only way up these days is job hopping anyways.
- treve 2y agoThis entire comment reads as someone who has a purely adversarial relationship with their coworkers with little trust. Sounds exhausting!
- manmal 2y agoSeeing you‘re a CTO, I‘m a bit concerned for your staff (if any) if your first reflex is blaming the developer for not trusting their boss.
- Huggernaut 2y agoI don't see any blame assigned in the previous comment.
- deleted 2y ago[deleted]
- solatic 2y agoI wish someone would solve my problem for me. I'm working on the problem because there are no solutions that I can just go and buy. Someone else putting their blood, sweat, and tears into solving my problem, they're the ones who have to deal with being on-call for it, they're the ones who have to maintain it, would be a joy. Why is it so important for you to be the one to solve this problem? Why is it so important for your solution to the problem to be a business? Running a business is about creating value for yourself and for your customer - if you're obsessed about the problem, be thankful that someone else is putting so much effort into solving it; if you're obsessed about the customer, then you would've shipped something to the customer a long time ago to get feedback.
- ZaoLahma 2y agoI guess some solo dev engineers hope to implement a novel idea, curate the implementation into a somewhat successful business (have a firm grip on the market) and then sell it all off to a bigger fish and make bank. I don't think many people actually want to run a business (long term), but most of us wouldn't mind suddenly being paid a good chunk of money for having solved or worked on an interesting problem.
- thekitze 2y agoin my case, I would never sell Benji to anyone else because my life literally depends on it. The business part is hard tho.
- thekitze 2y agoauthor here: for me it was important because after a while the app I was using was stale and wasn't shipping updates anymore. Also, as I was learning more about productivity, I reached the limits of the app. I wanted more features and I was coming up with tons of ideas that I could implement into my app, and other devs wouldn't care about implementing these ideas. I wanted control. So I finally shipped Benji (https://benji.so https://benji.so)
- pacifika 2y agoThere’s usually room for more than one implementation of an idea, most of the target audience haven’t committed yet?
- raincole 2y agoPerhaps it's just me, but I can't stand the "I'm trying so hard to be funny" writing style.
- pm90 2y agoAgreed. It’s very exhausting to read. A few well timed digs are ok but you need to not overdo it.
- thekitze 2y agoit's not just you, people have different preferences and that's fine :D
- netmare 2y agoI'm also not a fan of overly-funny writing, but I just wanted to say that I found your style quite enjoyable. Maybe it's because a can relate somewhat to your situation... :b
- StopHammoTime 2y agoIt's unfair he didn't include the name of the app in the article (or it's unfair that I can't see properly, if he did). I want to see what this problem was he was trying to solve!
- zogrodea 2y agoThe author posted a comment here about that, and that this article is about https://benji.so/ https://benji.so/ . Sounds like HN comments were persuasive in releasing the app that triggered the article. Comment: https://news.ycombinator.com/item?id=40872817 https://news.ycombinator.com/item?id=40872817
- aorloff 2y agoShipping code is a whole separate product from your product Its your first devops product, and how well you do that is going to affect your actual product
- andrewstuart 2y agoI've got three separate applications all "close to finished" and I've been working on them for years (along with many other things). Just as I'm getting real close to being finished enough to release - something changes - life changes - or some other thing changes - or I don't believe in the product any more - then I do believe in the product again - then blah blah blah. Always "legitimate" reasons - outcome always the same - haven't shipped anything in years except a bunch of open source projects.
- thekitze 2y agoSorry to hear that. As someone who actually shipped a lot of things, i'm still going through the "I believe in it" and "don't believe in it" cycle almost daily. Don't let that stop you.
- edg5000 2y agoI found that becoming an actual user of your own system changes the perspective entirely. I had this thing that I was making for myself, and it was not ready, not usable at all, or so I thought. After giving up on the project I decided to try and actually started using it as if I was a user. I realised that as users, we are used to countless minor issues, and we automatically find ways around that. When you are the creator of something, you sometimes forget that a lot of sloppyness will not be a dealbreaker, and the user will effortlessly work around many of the shortcomings. Obtaining perfection is more about ego at that point. So trying to actually use it, ignoring that you are the one who made it, and forbidding yourself to make any modifications for a while, can change everything!
- knallfrosch 2y agoInteresting point. An app I just used had an embedded ios web browser that didn't work properly. I opened the web page directly and used it like that. The username/password were iCloud-synced, of course. Took me all of 5 seconds to resume the user flow in Safari (which only took another 30 seconds to finish.)
- thekitze 2y agoI 100% agree with you.
- tstrimple 2y agoI think this is why ship it and iterate fast is often the best path. There will be deal breaking bugs in any software project. If your accounting package doesn’t account correctly, you probably shouldn’t just ship it. But if one of the reports displays twice for some reason, users can probably deal with it until the next iteration as long as that next iteration isn’t months to years away. But the reality is you wont even find what most of the “bugs” your users will encounter until it’s out in the wild with real users. And unless you ship it, you’ll not get to work on the bugs your users are actually impacted by.
- blackbrokkoli 2y agoThat's a cool take, thank you! I think it's something that I already knew in my heart, but I think by putting it like this you killed some shipping anxiety and perfectionism tendency in me. Thanks :)
- langsoul-com 2y agoIsn't this more a lesson of keeping your cards close to your chest? There's a very good reason why people are on guard with pitch decks. Cause those very people you pitched could just take the idea and throw money at it.
- shalmanese 2y agoNo, almost certainly the other people didn't start the project because they saw his video and were so inspired by the idea they rushed off to build it. Almost certainly, it was a case of parallel evolution where they faced a similar problem and there are only so many parameters in the design space so they figured out a similar solution. People who focus on ideas think their ideas are so inspirational and unique that they must be protected. In reality, anyone who has tried to go out actively and convince anyone else to build their "brilliant" idea quickly realizes the level of indifference and lack of engagement anyone else has to your baby.
- rob74 2y agoThat "those guys" may have seen the video he posted was just an unsubstantiated suspicion of his though. The sad part about having brilliant ideas for apps (as I have also found out, fortunately before putting a lot of effort into the idea) is that there are millions of other developers in the world, and one of them is almost guaranteed to have had the same idea a bit earlier than you. Unless it's a super niche thing, but then the market for it is also super tiny...
- thekitze 2y agoAfter years of building in public, I'm scared that you're right. But the problem is, my app is now live (benji.so), and it's publicly out there for people with VC money to start copying features from it ...
- purple-leafy 2y agoI highly disagree. 99.99% of peoples SaaS ideas aren’t innovative. It’s more about the people, their resources, their experience. I’d say this is a misinformed opinion, maybe from lack of experience.
- rob74 2y agoSo, he's a fan (and paying subscriber) of his "competitor" app now, but still not enough of a fan to actually mention what app it is. Which is kind of frustrating, I read until the end of the post to see if it's mentioned, but it isn't. And it also leaves me with a nagging suspicion that the whole story may just be completely made up (or at least grossly exaggerated)...
- thekitze 2y agoIt's not made up, I'm not using the competitor app for years, and I didn't want to give them more attention because this space is super competitive.
- deleted 2y ago[deleted]
- thekitze 2y agoAuthor here! I need to update this article. Years later, I actually got motivated by the comments on HN (whenever this gets posted). P People are always like "why don't you just ship your app?" ... so I did! I'm happy I went through with and it's way WAY better than any competitor in this category Check it out at https://benji.so https://benji.so (landing page is still w.i.p)
- rob74 2y agoHi! Looks great, maybe I'll give it a try... Is it named after this guy https://en.wikipedia.org/wiki/Benji https://en.wikipedia.org/wiki/Benji ? I was a huge fan of him (them?) when I was about 6-8 years old! ...and sorry about expressing my frustration (and suspicion) about you not mentioning the name of your "competitor"! I guess now that you have released your own app, the chances of you mentioning it are even smaller (if it's still around at all)?
- thekitze 2y agoIt's named after my dog Benji haha. Yes you're right, I'm not gonna mention any competitors, especially on a viral HN article :) There's a chance I might make a /comparison page in the future though.
- pantulis 2y agoI just tried it and the detected timezone for me is called: "Africa/Ceuta (Romance Standard Time) (UTC+01:00) Brussels, Copenhagen, Madrid, Paris" While the assigned delta with GMT is correct, this is confusing as hell because neither Brussels, Copenhaguen, Madrid or Paris are in Africa. You may want to take a look at the TZ info you are using. EDIT: See comment below, this is not an issue.
- com 2y agoBut Africa/Ceuta time aligns with CE(S)T for longstanding national administrative reasons, I believe. That’s why those other cities are listed, since Africa/Ceuta time is not linked by policy, regulation or legislation with any African time zones… Time is one of those human constructs that isn’t strongly bound to geographic or perhaps even physical reality. Look at the International Date Line or Chinese timezone maps for examples that are “bigger” than Africa/Melila and Africa/Ceuta. We should all be glad that people are thanklessly doing the hard work to keep the TZ databases updated.
- neontomo 2y agoan added benefit of shipping early is you get a feeling for whether people are interested, before you spend a year developing a toaster that eats its own toast.
- protocolture 2y agoI have a loose product idea. I guess the difference between some ideas and others is in prototyping. My prototype works. The issue is that the market for the product is like maybe 600 people global. And its not just code thats required, but plastic injection moulding, hardware manufacturing etc.
- dazhbog 2y agoHow do you know it's 600? what would be the sale price? Sometimes with a little modification, a hw product can work in multiple b2b verticals ;) Ive done a few products myself with injection molding, production pcbs, etc. and it's amazing how different customers look at it and ask for different features.
- protocolture 2y agoSuper niche, combines 2-3 other products that are individually expensive and dont have any real reason to be together.
- DidYaWipe 2y agoI'm expecting to experience this any day now. I've experienced it before, seeing people make hundreds of millions of dollars on an idea I'd already built (and my employer had fumbled the marketing of) and was actively working to resurrect... but couldn't figure out how to "monetize." Currently my problem is being a one-man band. I've realized I can't "just ship" a product that relies on a hand-rolled user-authorization scheme that I create with very little experience. So now I've interrupted my whole project to learn Supabase and oh yeah, containers... because I've never used those either and as far as I can tell I'd better use those for deployment and scalability. And oh yeah, I had to learn SwiftUI (already knew Swift & iOS pretty well) to write the app... and also JavaScript/TypeScript and Deno for the back end. So now I'm entering year two and still trying to vacuum up knowledge fast enough to get this thing out the door before someone else announces it. I've been thinking that I'd have to hire someone to consult on security and scaling as I finish up actual functionality. But the days go by...
- jezek2 2y ago> I've realized I can't "just ship" a product that relies on a hand-rolled user-authorization scheme that I create with very little experience. Time to ship and get the experience :) It is probably not that bad as you think it is. You can also ask others if they see any obvious security/cryptography fails and you would do better than most including big companies... > So now I've interrupted my whole project to learn Supabase and oh yeah, containers... because I've never used those either and as far as I can tell I'd better use those for deployment and scalability. Please don't. Leave it for later if it is truly needed. You can ship without. Don't be lured to the clouds, they're too expensive and you will need to learn and change a lot. Instead use VPSes and/or dedicated servers from cheap providers such as OVH/Hetzner. Just running your server app on a normal Linux VM is a way simpler than any cloud solution. It can also handle quite a lot, it might surprise you. And you wouldn't get insane invoices for 10-100x overpriced traffic that the clouds have and that kills many ideas even when it would make sense to do them in the cloud otherwise.
- DidYaWipe 2y agoThanks for the advice! I did run a somewhat similar app with essentially no API security on a cheap-ass Linode VPS around 2011. But we only had 10-20K users and those extremely sporadic. But, although users controlled their content, it was totally anonymous. I didn't require a single credential, not even an E-mail address. One thing about Supabase is that it's supposed to offer user verification through E-mail out of the box, which saves me the time of hand-rolling that. The reason I want containers is to spin up multiple instances if the thing blows up. Isn't it easier to do that with containerized services?
- purple-leafy 2y agoOkay I gave up reading because it’s written by a man-baby. So cringe. So you made a proof of concept and rested on your laurels. Too bad, that’s life. They did the work and reaped the rewards. Lesson learnt. You can’t claim ideas
- xlinux 2y agoThe real problem I face is finding users. you are not allowed to post your app anywhere (excluding hn). It's called advertising or spam they say
- pjc50 2y agoThere's hundreds of thousands of apps. People aren't going to invest any effort in evaluating them.
- rawbert 2y agoWhen I read this I was like "Oh, that sounds like my family calendar / collaborative productivty app I am working on for months ". And in the last sentence he mentions > I wanted an app that combines Todos, Habits, Planner, Goals, Pomodoros, Meal tracking, Fasting, Hydration, Packing, Trips, and many many more features. Surprised Pikachu face.
- torlok 2y agoNot the best example of "just ship it". The thing about these productivity apps (TODO, habit tracking, spending tracking, journaling, workout planning etc.) is that lots of people have these ideas independently. You can't imagine how clever I felt when I thought of the idea of an app that helps you keep track of your expenses. Then I checked the Play Store. KRAZAM even made fun of it the "The Hustle" video 5 years ago.
- realharo 2y agoYeah, this is probably the most overdone app category in the history of overdone app categories. That's not to say that a new twist on it can't be successful (most successful things aren't entirely original), but if you're worrying about someone releasing their version earlier and beating you, just take a look around.
- satvikpendem 2y ago> Then I checked the Play Store I think you missed the point of the article, which is to ship it despite competitors; in fact, competitors validate your idea, it is a good sign, not a bad one.
- deleted 2y ago[deleted]
- spacecadet 2y ago"If you have an idea, statistically 1500 other people are also having that same idea" Execution trumps ideas. It also does not need to be fast! I have seen it go all ways at this point, and I still stand by another stupid quote, "slow and steady wins the race". The real problem lies in whether you mature your idea into something with long term value. If you ask me, fast ideas, fast execution = garbage in, garbage out.
- dspillett 2y agoIf I was writing something for myself, I'd not be sad that someone had beat me to it: it just proves that the idea was a good one! Then again, none of the many personal projects I've got in my head and on paper (few of them even actually started) are ones that I would release to sell. They are things that I want or that friends/family/other might find useful. Heck, if I had something Alpha quality maybe I'd release that in the hopes someone would see it and think “this idea is useful, but the implementation is shite, I'll write a better one”.
- nyokodo 2y ago> If I was writing something for myself, I'd not be sad that someone had beat me to it The reality is that you’ve already been beaten to the punch by something in almost every situation. If you’re automating something for the first time in history then the preexisting manual method is your initial competitor. In the case of the app in the article they’re competing against that other app but also every other possible patchwork of partial solutions that their target customers are already using. Additionally, if you are the first mover then you’ll quickly have competitors rise up and eat away at your advantage without your effort to stay ahead competitively. So, since you’re always scooped then don’t worry about being scooped and since competition now or later is a certainty then instead focus on your competitive advantage. The author came to this realization in the end, bravo and good luck!
- black_13 2y ago[dead]
- omerhac 2y agoHahaha, laughed my ass off. Can you name the largest factor to why you did not ship it? Is it fear? shyness? Thinking that you only have 1 chance with your clients?
- SergeAx 2y agoWhat do I feel like I just read an advertisement article for a productivity app?
- RevEng 2y agoWhat was your purpose in developing this app? It sounds like you were trying to solve a problem you had for which there were no other good solutions. If this was the primary purpose, then it's only meant for you and not for anyone else, so why "ship it"? For personal use, shipping it simply means using it. If you want to produce a product to sell, then yes, for the most part you want to ship as soon as you have a minimum viable product - something that at least accomplishes something valuable, even if it could be better. But if you're working on something for fun and you consider open sourcing it, don't rush into shipping it. As soon as you release it to the public, people will start hounding you to fix bugs and add features. If you try to please them, you'll quickly find yourself working a part time job for no pay - your hobby will turn into a burden. Releasing anything to the public - whether for profit or not - opens you up to a lot of pressure and judgement. You are making a commitment, whether you intend to or not. Before shipping it, think carefully about whether you want to commit to supporting it. If not, then just keep it to yourself. Giving up on a project - even one that works - isn't a bad thing. People change. Just because you wanted to work on it 6 months ago doesn't mean you want to do it now. Don't feel obligated to keep doing something you no longer enjoy. Often the important thing is that you went through the process - you learned a lot and you overcame a challenge. You can leave it at that and still be a success.
- ozim 2y agoI am a bit snarky but it is yet another todo app. Author is a bit high on his own supply - he thinks someone copied his great ideas where I see it as generic silly widgets. So of course he thinks it is great so much that people will love it … but just reading the thread I see the other app he was paying for stopped implementing features, because no todo app is „super great idea”. Well good job implementing, good effort, but that’s just „yet another todo app”.
- thecleaner 2y agoBut what's the problem that is being solved with a productivity app ? I actually use a spreadsheet program for this and it does a better job than most apps. I don't it matters what "the vision" is really.
- luna4151 2y agoIn order to be able to spy on someone’s phone entirely having access to their WhatsApp and seeing every incoming/outgoing calls and messages, I will recommend the service of professional hacker ( : ( TECHSPYMAX AT GM A1L C O M ) to successfully help you spy on the target’s phone just like he did for me when I was so desperate to look into my cheating spouse’s phone to find the truth. I was lucky to come across them and they got me full access to my spouse’s phone without her knowing and I was able to monitor the phone remotely, I saw all the text messages, WhatsApp messages, social media accounts including pictures and her locations. They are legit and reliable. Relay all your problems to them and you will be assisted good. You can reach them via the MA I L provided contact information above;