I kind of hate the profanity being part of the branding, or anywhere else that I’m going to use professionally. It’s pretty useless since it’s not actually describing the service (what exactly does “no bullshit” mean for forms?), and just detracts it and the team or developer who made it.
For me it sends a very clear message about both the intent and the delivery that I can't find a good substitute word for. I think you are being quite the prude!
Show HN: I built a free forms service for static websites
91–100 of 112 posts
Re: Show HN: I built a free forms service for static websites
#92Earlier quoted context omitted.
If a business cannot afford $100/year for a critical service, the business is not viable. Or to put it another way, if a forms service is not worth a large multiple of $100/year, it's not worth having a forms service.
A forms service is not just useful to businesses. I'd love to have a real contact form on my website, but it's all static and I don't really want to run the infrastructure myself. $100/year is _way_ too much for that case.
It’s not worth building a business for unprofitable customers in general. A forms service falls into the general case because a million customers is a highly unlikely. It’s also likely to require an undesirable business model. For example $10/site/year is going to be too dear for people with multiple hobby sites if $100/year is too dear.
Re: Show HN: I built a free forms service for static websites
#93Here's how to post to a Google Form: https://stackoverflow.com/questions/18073971/http-post-to-a-...
Re: Show HN: I built a free forms service for static websites
#94The forceful over emphasizing of "Free. no bullshit" throughout the website is off putting
Re: Show HN: I built a free forms service for static websites
#95Re: Show HN: I built a free forms service for static websites
#96I kind of hate the profanity being part of the branding, or anywhere else that I’m going to use professionally. It’s pretty useless since it’s not actually describing the service (what exactly does “no bullshit” mean for forms?), and just detracts it and the team or developer who made it.
Keep in mind that the concept of profanity varies greatly from region to region (and audience to audience). For example, where I live, "f k" and "c t" are fairly common words to say. But ironically, expletives including "god" are shocking.
Re: Show HN: I built a free forms service for static websites
#97Earlier quoted context omitted.
On the other side, I'd love an indie-accessible service where I wouldn't pay more than a total cost of a cheap VPS and a domain for a single SaaS which forms like a 5 % of user experience. It seems that everything is either pay-with-privacy, or $100/year, with no middle ground, and that's sad for me as an indie. (Btw, I am trying to fit into this gap with a $1/mo subscription for a commercial-quality weather forecast…
the difficult part is finding the right perk that divide the users from indie and professionals. for something like git number of accounts or private repository count can be enough of a signal to act as differentiation in plans, but for something like forms it's going to be hard, maybe authentication or sso, idk.
Re: Show HN: I built a free forms service for static websites
#98I've been recently looking for form solutions Free https://www.staticforms.xyz/ https://formsubmit.co/ Paid https://formbucket.com/ https://formspree.io/ You can also check out Netlify Forms
Re: Show HN: I built a free forms service for static websites
#99Earlier quoted context omitted.
To make matters worse, the site is using third party trackers, so your data is already being abused the second you open with the site. Its also closed source. I may sound paranoid, but I won't be using the service.
In SaaS, you're not going to find many products that don't use trackers and are open source, as much as that may be philosophically interesting to see. I actually want a SaaS company to track my behavior so they see what's wrong, fix bugs, and improve the product as a whole.
Re: Show HN: I built a free forms service for static websites
#100Earlier quoted context omitted.
A forms service is not just useful to businesses. I'd love to have a real contact form on my website, but it's all static and I don't really want to run the infrastructure myself. $100/year is _way_ too much for that case.
Back of napkin calculation: assuming low costs, $100/year is on the order of 1000 users per software engineer if the engineer also does support. Make it $10/year and the engineer has 10k users to support. 10x users mean 10x probabilities of long tail support events. The long tail of support is unbounded in negative consequences while the best support interaction is zero bound. It’s not worth building a business for u…
> It’s not worth building a business for unprofitable customers in general.
I mean, Uber seems to be doing reasonably well.