4 ms·

> Things like usage-based billing, managing credits, LLM streaming (with session resuming), user behavior analytics, and integrations with multiple model provid

> Things like usage-based billing, managing credits, LLM streaming (with session resuming), user behavior analytics, and integrations with multiple model providers all add a lot of overhead before you can even focus on the product itself. That doesn't make sense to me. The product needs should dictate whether or not you need those things. You shouldn't be boiler plating them in without a product-driven reason. So if you found the need and are responding to that need... you are focusing on the product.

liurenju 1y ago
Thanks for your comments. We distill these features as our priority because our current product SellToSky needs them and we spent significant amount of time building it. We'll not re-invent the wheel but rather glue the available open source project + any missing parts. The whole purpose is to abstract the backend needs as a service -> reducing the repetitive works from the fellow AI developers/founders. That's why I am coming here to see whether any other developers or founders experienced the same pain?
- codingdave 1y ago
  The exact same set of pains, that could be solved by a single solution? Unlikely. You'd need to have more of a menu of services available, likely with variations of each. It might be feasible, especially as more people try to launch AI-driven apps without actually knowing what they are doing. But it is going to be a fine line between a back-end platform vs. just doing consulting gigs with potential customers. You would likely end up catering to people who are less experienced, as no individual piece is all that difficult, so experienced coders would just build it themselves. In particular if they are building a product whose primary transaction is AI-driven, conventional wisdom is to avoid buying 3rd party solutions for your core business value.

4 ms·

> Things like usage-based billing, managing credits, LLM streaming (with session resuming), user behavior analytics, and integrations with multiple model provid

by codingdave 1y ago

liurenju 1y ago
Thanks for your comments. We distill these features as our priority because our current product SellToSky needs them and we spent significant amount of time building it. We'll not re-invent the wheel but rather glue the available open source project + any missing parts. The whole purpose is to abstract the backend needs as a service -> reducing the repetitive works from the fellow AI developers/founders. That's why I am coming here to see whether any other developers or founders experienced the same pain?
- codingdave 1y ago
  The exact same set of pains, that could be solved by a single solution? Unlikely. You'd need to have more of a menu of services available, likely with variations of each. It might be feasible, especially as more people try to launch AI-driven apps without actually knowing what they are doing. But it is going to be a fine line between a back-end platform vs. just doing consulting gigs with potential customers. You would likely end up catering to people who are less experienced, as no individual piece is all that difficult, so experienced coders would just build it themselves. In particular if they are building a product whose primary transaction is AI-driven, conventional wisdom is to avoid buying 3rd party solutions for your core business value.