21–30 of 66 posts
Well that may be convenient for you but since these dashboards are external, does scalability become the responsibility of your customers? I can’t imagine thousands of users all hammering expensive analytical queries on a single unoptimized replica will scale very well.
How does it compare to Amazon QuickSight which also has a pretty strong embedding story. Thank you.
What setup are you using that makes quicksight work well when embedded?
Quicksight’s embedding story is worse than tableau’s. And tableau isn’t that great with embedding either.
There was a great thread recently on developer marketing here: https://twitter.com/nickwritesit/status/1402318187299934212?...
You should post again here and on producthunt when there’s self-serve signup and live demos.
The videos look good!
1. I see that startups pay $500/month. How do you compare that to Metabase which is $85/month (or $385 if you remove the Metabase attribution)?
2. Do you, or do you plan to, offer the ability to embed individual charts instead of whole dashboards?
3. Do you support custom chart creation via python/R?
4. Do you think Explo is a fit for our use case or a different tool: we're experts at SQL, good with Python, and looking to rapidly create and embed customer facing charts?
Please kill those progress spinners, the app is only rendering little bits of 2d art. Count each one as an individual statement of "you asked me for something but I haven't done my job yet, and now I'll make you pay for my laziness, and I promise if you click anything I'm just going to show you a million more progress spinners because I hate you and don't value your time"
Also please don't shoot the messenger, spinners were briefly an acceptable UI cue sometime around 2 decades ago, nobody honestly likes seeing them any more. If you explicitly design an app UI around the expectation of delays, it gives endless room to cut corners and add more delays. In other words it is optimizing the whole user experience for intentional mediocrity.
How does it compare to Amazon QuickSight which also has a pretty strong embedding story. Thank you.
Not trying to be rude but I’m curious what makes you believe quicksight has a strong embedding story? I’m generally a quicksight fan (although it has so many things it could do better with a little TLC). What setup are you using that makes quicksight work well when embedded? Quicksight’s embedding story is worse than tableau’s. And tableau isn’t that great with embedding either.
We allow users to customize the design of their dashboards using CSS and Markdown, and have design elements such as containers to group analyses together. We found that users were hesitant to embed Tableau, Quicksight, or other BI dashboards because they didn't fit into their application.
Also, Quicksight and a number of other tools require you to define a data model, create analyses, and then add them to dashboards. Our platform is oriented around the dashboard, so you write SQL, create visualizations, and design dashboards all in the same view. This gives users a lot of flexibility when creating dashboards and also speed up the time to implementation.
Earlier quoted context omitted.
To echo the above sentiments, no pricing is also synonymous with enterprise for me and I don't give any consideration to products without transparent pricing at all.
That makes sense. We are definitely not trying to hide an outrageous enterprise price tag. I responded to mchusma's comment with how our pricing currently works. Let me know if you have any specific questions about it and happy to dive deeper!
Clicked into one of the demos, was greeted by around 10 progress spinners, possibly more. This instantly reminded me of some combination of Google Cloud's deeply mediocre console and waiting for a Jira page to render. I'd simply never prefer a tool like this or see it fit to force someone else to use it, and I don't understand why anyone would intentionally design an app to behave like this. Please kill those progres…
I am curious your thoughts on a better way to approach this. My initial thought is for a single loading state which ends when all the data is ready to display on the page. It feels inevitable that there is some loading moment when we are fetching the data. It sounds like, based on your comment, that you would prefer there to be no loading state thought?
Clicked into one of the demos, was greeted by around 10 progress spinners, possibly more. This instantly reminded me of some combination of Google Cloud's deeply mediocre console and waiting for a Jira page to render. I'd simply never prefer a tool like this or see it fit to force someone else to use it, and I don't understand why anyone would intentionally design an app to behave like this. Please kill those progres…
Hi Explo team. Congrats on the launch! My previous company and my new company both provide insights as a service, so customer facing dashboards are the core product, and therefore this is very interesting to me. A few questions for the team: 1. I see that startups pay $500/month. How do you compare that to Metabase which is $85/month (or $385 if you remove the Metabase attribution)? 2. Do you, or do you plan to, offe…
1. We have a few customers who have switched over from Metabase for a few different reasons. The main ones are that we offer much more extensive UI components, more chart capabilities, better security guarantees, and highly customizable styles. While $500 is more than Metabase's price point, we believe that an embedded first solution is worth the price since it will save you 10-20x the cost per month on development and maintenance costs.
2. Yes! A dashboard is just a collection of one or more charts/UI elements and so if you make a "dashboard" which is just a single chart, you can easily embed that. We have many customers who have this use case to embed analytics granularly throughout their app.
3. Not currently, though I'd love to understand more about how/why you would want that. We've heard this a few times as a "nice to have" but would love to build it out with a customer that really needs it.
4. It sounds like you'd be a great customer for Explo! It takes all of the hard work of building out user interfaces out of the equation and makes it so that you just need to specify data queries with SQL and then use our drag and drop interface for UI building.