181–190 of 223 posts
http://flowgrid.org Idea was that on mobile, programming would be simpler graphically, taking advantage of the touch screen. It wasn't really. Or I gave up too early... ¯\_(ツ)_/¯
Earlier quoted context omitted.
> the visit to download ratio is low compared to my other 2 commercial products. Not sure why. I'm pretty sure the traffic is targeted, I am solving a real problem and the website explains what it does. Any feedback would be welcome! Who is your target audience (programmers, analysts, accountants)? What industries can benefit most from it? Your homepage is all about features and not about users or their problems.
>Who is your target audience (programmers, analysts, accountants)? What industries can benefit most from it? I'm trying to find that out. ;0) I think it is probably a non-programmer business analyst, marketer or scientist with lots of Excel or CSV files to munge together. But experience with other products tells me that you often end up selling to different markets than the one you envisage. >Your homepage is all abo…
> I'm trying to find that out.
You can start with why you use it.
So I built a backend service to send a push notification when available.
I was out there for a season and it was good but I didn't return the next year and I lost the urge to fix an issue I no longer faced. Was a great learning experience though!
I made https://www.hackersubscribe.com as a way to get email notifications when certain people post/comment on Hacker News. So I get an email with patio11, Patrick Collison, or Alan Kay posts. When I first made it, I submitted a Show HN thread, but got zero response.
First I'll explain what I mean by "failed". I'm not shutting down or ceasing development. But since I have a previous side project that never became profitable, I made an agreement with my wife that if I didn't get 10 paid users in February, I'd de-emphasize this project and focus on other things. So far I have 2 paid users, and they're both people I know. It's pretty obvious February won't see 10 paid users. Now the…
Earlier quoted context omitted.
About working with Spreadsheet as database ? About running it automatically etc..
I used Google Scripts for everything. Can programmatically read and edit a Google Sheet easily enough; true DB queries are trickier. Running is based on triggers you can set up for a script; or I think a script can programmatically set them up. Look up the Google Developer site; it's a good resource.
https://get.thread-app.com It's an ad-free social network that is supposed to be a richer and more private alternative to Facebook. It's been adopted by my closest friends and family, but hasn't grown much beyond these initial users. The product itself tries to do a ton of stuff: messaging, photo sharing, event planning, location sharing, video sharing, etc. Perhaps that's part of the problem -- it doesn't do one thi…
I've been running a very shitty threaded message board for years ("running" being a very loose term - I mean it's still there). There is a parallel facebook group that exists solely to tell me when I've f'd up. The people still on it, are the people who use it as a "separate space" to all the rest of the bazillion dollar alternatives - hellbent on shoving adverts, tracking and all the rest. I'm only going off on this…
It's here at https://aether.app/email/#/force. If that turns out to be your thing hit me up and I can extend the trial for you as far as you need to give it a shot.
Earlier quoted context omitted.
I disagree. Marketing gets people in. Users guide product development and thus the product. If an ”unstable product” is one that users actually want to use, then I guess an unstable product is a good thing?
Treating marketing as requirements gathering gets you overly complicated internally inconsistent requirements. The instability is side product. Marketing is not making trade-off between bugs and features, they are unaware of trade-off. When the "buggy" part happens, they treat it as "we have incapable developers" and not as reason to change something in process and requirements gathering. By overly internally inconsi…
I feel what you are talking about is a siloed approach where developers build what the marketing team promises to customers. If these teams are the same people you are the developer and marketing team, and thus over-promising things to customers is only shooting yourself in the foot.
Finished the project, built the tool and it worked great, had a bunch of people using it. Then I got to the point of having to actually distribute/market it and I gave up - the idea of having to actually support a desktop application was just too much for me.
I'll probably throw the code up on GitHub at some point so people can still get some value out of it, since a lot of people have been asking.
Since I happened to need to send & receive a fax, but didn't like to commit to a longer subscription plan, I made this website for doing that: https://5dollarfax.com/
I had a plan to promote it by writing a deep blog post about the contents of a fax handshake, and got pretty far into it, but at one point it required some signal processing knowledge I didn't yet have and the post languished.