51–60 of 91 posts
is this the latest pivot? are we going to see another completely different business in 3 months?
He is trying to build something useful, which may take some pivots, and that is nothing to be ashamed of.
is this the latest pivot? are we going to see another completely different business in 3 months?
I got very burnt once (in terms of time wasted anyway) by a startup that couldn't decide what it wanted to do.
They had an amazing BaaS product that probably was making good coin already that I am sure would have got them a buy out eventually but they decided to pivot to work on a DB abstraction layer and shut the whole thing down.
If they had just pursued the original vision they would be minted by now instead of trying to convince people their commercial layer is better than the umpteen other free ones.
1. Why would I trust that this will stick around if I make a business on this? 2. Why would I pay someone to "generate IDs" at $1/10k requests? 3. If the DB API was performant and supported full SQL, it looks like it would cost $business I know of two orders of magnitude more than current cloud spend to switch to it. (They would not, because of compliance.) For whom is this the right pricing model for? I compared the…
I'm probably missing something - some of these APIs I get, but some just seem useless. Why do I need an API to convert images? Find emojis? Convert "John" to "Hello John"? (ok the helloworld service is just a demo.) I can do that on the client using Javascript. Moreover, why this instead of something like AWS Lambda, where you code your own service? Instead of prebuilt APIs, why not make it more general? Don't get me…
1. Why would I trust that this will stick around if I make a business on this? 2. Why would I pay someone to "generate IDs" at $1/10k requests? 3. If the DB API was performant and supported full SQL, it looks like it would cost $business I know of two orders of magnitude more than current cloud spend to switch to it. (They would not, because of compliance.) For whom is this the right pricing model for? I compared the…
Some of these services are proof of concepts/placeholders while the others are coming out of the pipeline. So their price is not necessarily final either. Admittedly the "library as a service" ones are more for niche use cases, like how I go to a website sometimes to get the current Unix timestamp. If you want an example $X_FORMAT id, paying 1/100 cent for it is no big deal.
How do I create an API to offer on the site? I don't have one right now, but I know from experience the kind of API's that people need but don't want to deal with creating from scratch themselves.
(Maybe save that for 2022-04-01.)
Question regarding "Sell your APIs on Micro." If a developer makes an API and it becomes popular on Micro, what prevents Micro from cloning that API and cutting the dev out of the proceeds?
Why do support, q/a, maintenance, performance improvement for hundreds API with thousands of quirks when you can sell shovels as if they were made of gold? In a similar vein, how much visibility does micro API bring to my API compared to established platforms? Even assuming it's a lot, why not just publish my API on all of them?