3 ms·
Sometimes I imagine what it would look like if an old-school piece of technology like Sqlite had a buzzy marketing homepage. "The power of SQL meets the simpli
by dgreensp 4y ago
Sometimes I imagine what it would look like if an old-school piece of technology like Sqlite had a buzzy marketing homepage. "The power of SQL meets the simplicity of a file. In your pocket." And the entire page would be a dozen taglines in large font at that exact same level of specificity.
This seems very similar to Apollo at the pitch level: GraphQL/graph-based backend architecture, free tools, sell backend software and services. The logo is even extremely similar to Apollo's. Apollo sells software to enterprises that have adopted GraphQL and do a lot of GraphQL. When you move away from that, the app framework/BaaS "market" is very crowded. Everybody wants a piece of the backend these days--the privilege of running some short or generic code for you in a datacenter for a fraction of a penny, with the promise that it's "easier" that way. Bouncing each user request between five different data centers (Auth0, application server, datastore, etc) is actually kind of slow, though.
I think it should be more clear from the landing page what is novel here; what differentiates it; what is a killer feature or moment of delight you can't get elsewhere; who is it for.
- jensneuse 4y agoThank you for this feedback, very helpful.
- dgreensp 4y agoI’m glad, actually! I had some more direct feedback that I didn’t submit. It wasn’t clear at first, for example, if it uses GraphQL or offers an alternative that is as powerful (the answer seems to be “GraphQL or TypeScript,” whatever that means). It says it’s a framework for any backend, but then the diagram has a special WunderGraph server in the middle of it. Most people haven’t thought about different ways to structure a backend, and even I (as someone who worked for Apollo, though right before it became Apollo) am not totally sure what it means to compose APIs using a graph. Or “transform a database into a toolkit.” A lot of full-stack developers still have only a vague notion of what Apollo does, I think. Also, does this new thing enable best practices and make them easier? Or is it trying to supersede best practices with new practices? I think a lot of education is in order.