I worked solo for three years on a 3D cyberpunk shooter all in a custom C++ engine. It was a hybrid single/multiplayer idea, where you would progress through the campaign and encounter other players at the same time. The twist was, in keeping with the cyberpunk theme, once you got to the end it would be revealed that all the players were actually bots the whole time. At first I was going to commit 100% to the decepti…
A game where bots turned out to be real players would have been fascinating though.
Ask HN: Show your failed projects and share a lesson you learned
101–110 of 285 posts
Re: Ask HN: Show your failed projects and share a lesson you learned
#102I originally started it to scratch my own itch. I wanted a notification from my temperature sensor when my new born son's room got too cold (we didn't have AC, so we left the window open).
I knew solutions already existed, but I wanted to get better at programming. Which I did.
Pushback has a little bit of everything and has been rewritten 3 times going from:
- go to rails to hybrid
- puppet to k8s to Ansible
- most react native libraries and their successors
- Hugo to Gatsby
After all of that I thought, hmm maybe I should make this a SaaS. That sparked interest in business development, which I learned a ton. Did startup school 2 times, but still didn't make hardly any money.
Eventually I cut my losses and made something new, Tellspin. I did everything opposite of pushback with my new product.
- landing page first
- didn't write any code of the actual product until I had initial user interest
- chose boring tech
- stopped chasing shiny things
- spent a large portion of time doing marketing rather than building the product.
Tellspin has made way more than pushback in a third of the time. In fact, I don't think I'm even close in terms of hours spent. I'm pretty my hourly rate on pushback's is like $0.001 per hour.
With tellspin, all I did instead was focus on getting interest, talking to users, and distribution.
When a customer gave some feedback, I spent more time on the product. Then went back to marketing.
At this point, I'd say I've spent about 50% time on product, 50% on getting the word out there (blog posts, SEO, guest posts, etc)
Hopefully that's helpful to the ambitious people out there. Your product might be great, but if you focus too much on tech, no one will find out about it.
I wrote a detailed one year retrospective on tellspin's blog if there's continued interest in what I did. Nothing special really, just talking to customers and solving what problem they have.
Re: Ask HN: Show your failed projects and share a lesson you learned
#103Earlier quoted context omitted.
> our app was just extra work Just this week my kids basketball coach is trying get all the parents to "use the app" for scheduling and announcements and its just NOT working so back to email which works for everyone. As both a player and in the past as a coach, my experience with "sports team apps" has been that nobody wants to be the end user's IT department and on any team with more than X players the odds of some…
Could you give me some examples of what you would think would be needed? Have a sister whos kids are going to be getting into sports and feel like this would be a fun side project
So if you're one of the minority of parents smart enough to import a calendar into their google (or other) calendar, they can get the game schedule there, but the less competent (to put it nicely) can continue to get a stream of emails or even plain old text messages of upcoming games. Or they could join a FB group or a different platform.
Or there's people out there whom could never handle installing or using slack, but if you could spam them text messages maybe they could still participate, or even participate fully.
Nobody wants to work in IT, especially not for free.
We went thru an internet era, then a social era, then the era of notifications, and I have a gut feeling the next era is going to be something like smooth automatic operations across semi-hostile deeply silo'd platforms, but it'll have a cooler name. FB wants to replace the internet with FB, but literally nobody else wants that, repeat for all platforms, meanwhile you get 5 users together somehow you'll get 6 preferred platforms, the next era will be anti-vendor lockin. People old as me will remember when Ma Bell provided both your phone service and your physical phone and times were better post-divestment and that's probably how we're going to look at the past once we're beyond the era of the social media silo. Rather than "the world is viewed thru my website for my profit" the future will be something like "the world is viewed thru my REST API or maybe many other API providers" And where the profit comes from is mysterious. Likely the gateway tech will be workable microtransactions. Such that every time Sally Softball Mom checks the team schedule she will get billed and you will get a hundredth of a cent, which isn't going to scare away 10M daily users but would be a nice side gig for you personally. Assuming you get 10M DAU of course.
Re: Ask HN: Show your failed projects and share a lesson you learned
#104Robintwits Based on the Robinhood API, I attempted to merge Stocktwits API to create hype stock trend analysis platform. I wanted to combine both the buy side and hype side of these stocks into a very basic analytics platform. After Robinhood shut down their unofficial API my project was dead. Also Stocktwits are quite restrictive with their API use now, I believe. Lesson learned: Platform risk is an obvious threat t…
Re: Ask HN: Show your failed projects and share a lesson you learned
#105Learning - no one really needs help doing this :)
Re: Ask HN: Show your failed projects and share a lesson you learned
#106Which is to say, with the benefit of hindsight, I did not do sufficient product-market discovery and validation upfront before I went "all in" on it.
I/we got sales but it never came within even an order of magnitude of how much FT engineering salary I was missing out on. By some metrics it was a success but by net USD impact on me it was a fail.
Was a great experience and I learned a ton though.
Re: Ask HN: Show your failed projects and share a lesson you learned
#107Re: Ask HN: Show your failed projects and share a lesson you learned
#108I launched ByteVitae ( https://bytevitae.com/ ) a couple of years ago, got a decent launch here and in Product Hunt, a bunch of users the first days ~3500 and a steady influx of users over the following months. I didn't know how to convert most of those users to clients, didn't talk to them, lost all interest after the initial launch and moved on after an amazing -26€ in benefits :P I learned so many things and was s…
Right!. But did you inform your customers that You were shutting down, what did you do with all the Datum that you collected(User Auth). Did You give them the opportunity for them to properly delete their account data stored on some DO droplet VPC waiting to be harvested?
Once I decided I was going to kill the project, I removed the option to become a paying customer to not get more, waited for the last of my paying customers period to finish (it was a yearly subscription). And released an update that made the app work strictly locally, user data does not reach my server (edit: there is no server anymore) and stays in the user's browser (it works like that now).
Kept the data for a couple of weeks in case anyone wanted to recover it to help them use it with in the new "local" version, but enventually no one did, so finally I deleted my db. So right now I have no access whatsoever to that data.
Re: Ask HN: Show your failed projects and share a lesson you learned
#109Mine is rather unconventional. Started a side project ( https://javfilms.com ) that aggregates popular Japanese adult videos (NSFW site by the way). It didn't fail, but it never picked up to a substantial point.
Re: Ask HN: Show your failed projects and share a lesson you learned
#110Had several: last minute airline seat bidding app with an interested airline. Fishing competition app with paying users. Housing valuation app for a city council, with the actual city council interested and opening up their API to us. The city council also wanted a parking app and water billing app. A telco requested a reloading app that was basically CRUD but offered 6 digits for a few days of work. There was a diet…