431–440 of 476 posts
Earlier quoted context omitted.
Have you thought about building the reverse application? A service that screens out all throwaway emails so only users who register with a real email address can use a service.
That's pretty much an impossible to win game of cat and mouse
I created https://SauceNAO.com , a primarily anime focused reverse image search engine in 2008. While it's purpose has never really been to make money per se, it's been extremely expensive to operate. It's been pretty successful usage wise, but paying users are another matter entirely. Donations and account upgrades keep the lights on, barely covering the hosting costs of the main collocated front-end server, but lac…
Earlier quoted context omitted.
This is a common mistake: building a product based on assumptions, and not on the market's demand. I've learned not to add a feature before I have someone who paid an advance. Secondly: your product might be to overwhelming and doing to much; experience has thought me that complicated products are a though sell. Try to reduce it to it's most basic use-case, and sell that (a simple app that doesn't require any explana…
>This is a common mistake: building a product based on assumptions, and not on the market's demand. I've learned not to add a feature before I have someone who paid an advance. I first came across this sort of advice here: The Montana Mogul: RightNow CEO Greg Gianforte (Part 1) http://www.sramanamitra.com/2008/07/31/the-montana-mogul-rig... Interesting story. RightNow was later sold to Oracle, IIRC, for a good amount…
Earlier quoted context omitted.
I've build a wine tasting event app a couple month ago. Replacing the tasting sheet for tasting events with a simple web app to make it easier for the organizer to collect and analyze feedback and market after the tasting. Got a few hundred users but no real traction yet :-/
Can you share a link? Would like to check it out.
Still 'beta' but you can signup under /signup/ Please share feedback :)
I've maxed out a couple credit cards and spent all my severance pay etc. trying to finish building this '3D abstract visual debugger,' which I'm calling Lucidity [video]: http://symbolflux.com/projects/avd I started working on it in 2014 and it's been on my mind ever since. I applied to YC with it a long time ago (was not accepted, and I can see so much wrong with the application I sent now...) I was laid off in Nove…
Nice! It would be interesting to visualize a React hierarchy this way. Is your display client using some sort of "open" protocol that you could hook other things?
> Is your display client using some sort of "open" protocol that you could hook other things?
Pretty much, except it's technically the server which does the rendering etc., and the clients send over information about data structures (as JSON 'operations' which say thing like add/remove to/from some position in a data structure). It probably would not be very hard to write a client which observes React programs and sends that info over.
I built Dependabot ( https://dependabot.com ), a service that checks your dependencies are up-to-date every morning and creates pull requests for you if they're not. Intention was to make dependency management suck less, whilst also adding a bit of runway to a bigger startup I wanted to do. * Spent 2 months building it - much longer than I'd thought. The work required to get from a prototype (2 days) to a SaaS produc…
That's pretty cool, I have been thinking of building something similar, but for Python. How hard is it to add new languages? What is the tech stack? Does it cost much to keep it running?
Earlier quoted context omitted.
This is a common mistake: building a product based on assumptions, and not on the market's demand. I've learned not to add a feature before I have someone who paid an advance. Secondly: your product might be to overwhelming and doing to much; experience has thought me that complicated products are a though sell. Try to reduce it to it's most basic use-case, and sell that (a simple app that doesn't require any explana…
>This is a common mistake: building a product based on assumptions, and not on the market's demand. I've learned not to add a feature before I have someone who paid an advance. I first came across this sort of advice here: The Montana Mogul: RightNow CEO Greg Gianforte (Part 1) http://www.sramanamitra.com/2008/07/31/the-montana-mogul-rig... Interesting story. RightNow was later sold to Oracle, IIRC, for a good amount…
I built https://callmom.pro/ this year in anticipation of a Mother's day rush. The idea is that we'll call you and your mom once a week at a set day/time in such a way that your phones both ring and when you pick up, you're talking to each other. The site is janky AF because I'm still in the neophyte stages of front-end/css. I do still think it's a good a idea, so I'm planning a revamp of the sales site in time for a…
It is a great idea. I am not sure it can make money, but it is genius. Have you thought about making the ring time random rather than set?
Then I thought I'd want to exclude the middle of the night (don't want to give people heart attacks thinking somebody died). Then I thought of excluding the work day (who wants to sign up for a service that will randomly call them in the middle of meeting?). Finally I decided it would be easier to set a specific time.
Maybe you're right though. Maybe the angle of "we'll keep trying until we find a good time for both of you" would sell better.
I've maxed out a couple credit cards and spent all my severance pay etc. trying to finish building this '3D abstract visual debugger,' which I'm calling Lucidity [video]: http://symbolflux.com/projects/avd I started working on it in 2014 and it's been on my mind ever since. I applied to YC with it a long time ago (was not accepted, and I can see so much wrong with the application I sent now...) I was laid off in Nove…
Your visualizations empower the livestreaming coder.
Also all of the YouTube channels that put up tens of programming videos every month. I'd love to watch coding tutorials and courses that use that kind of visualization.
https://theothermail.com TheOtherMail generates throwaway email addresses so you can try new products and services with no risk. We deliver all emails from your generated accounts to your personal email address so you don't have to remember stupidly long emails. We spend a few dollars per month to run it, and we haven't made any money yet. Give it a try!
Have you thought about building the reverse application? A service that screens out all throwaway emails so only users who register with a real email address can use a service.
Our service included feature to disallow disposable email addresses from registering. We typically sent an email validation, if emails were returned or not responded, we will flag those services to be manually checked and added to do not register list. We eliminated over 95% of registration with disposable email.
Solution doesn't need to be perfect in elimination, just reduce the problem enough so that it can be handled manually.