Hey all. We're super excited to introduce our new platform, Embeddable: a developer toolkit for building fast, interactive customer-facing analytics directly into your product.
It generates a no-code dashboard builder for you, powered by the components and data models defined in your code repository.
I've linked to a video showing how to use the SDK, no-code builder and how to build a dashboard.
Happy to try and answer any questions you might have.
Thanks @warrenm. That makes a lot of sense. The problem is that that feels like we'll have to throw away the "looks like a nicely integrated part of our platform' requirement.
Really good point about bug fixing affecting engineer morale. Super important.
One (arguably positive) side-effect I'm wondering might be possible is that: if bugs are always prioritised first .... and engineers are often very creative at solving problems .... will they perhaps come up with creative ways to reduce bugs in the first place?
Or, it might go all wrong -> and we create a dangerous culture of "swallow that exception" :D
When customers aren't signing up because of lacking feature -> build features.
When customers are churning because of bugs -> fix bugs.
Else -> somewhere in the middle
That's a really good point. If your userbase is feels listened to (which is admittedly easier in B2B than B2C) then these decisions become much easier.
"in practice this just means 3 or 4 levels of bugs that will never get fixed" - this is so spot on! This is exactly what we were thinking: realistically, if we don't fix it now, it will never actually get fixed.
So, if it's important enough to fix, why not fix it now.
We use a number of 3rd party APIs, and the problem we hit was knowing which to trust, which were reliable and which could be counted on.
I'm obviously not talking about your Googles / Twilios / Auth0s / etc. I'm talking about the longer tail of services that we don't want to build ourselves, but that there isn't instantly a big name service that provides it.
We would try one or two, and then find that they would work great in testing, but when you put any kind of load on them then they would regularly fall down. Similarly, when you reach out for help - while you're in the buying phase, they're very responsive - but as soon as you need support, you're looking at days not hours for a reply.
Perhaps in-person was the wrong word. "Present" is perhaps closer to what I meant. We want our presenters to have an audience. We want audience participation / questions / feedback. We want to create a buzz. ;)
Not saying that YC's format doesn't achieve that. It's just different.
But either way - totally see your point on posting it online afterwards.
It generates a no-code dashboard builder for you, powered by the components and data models defined in your code repository.
I've linked to a video showing how to use the SDK, no-code builder and how to build a dashboard.
Happy to try and answer any questions you might have.