rogansage
Why not to use iframes for embedded dashboards
HighCharts (JS Charting Library) User Guide
Rajiv Ayyangar, the CEO, claims that "no one wants to sift through 200 products per day" ... "it would be impossible for a good product to rise on its own merits", but users say this has effectively made it impossible for good products that aren't one of the ten selected by his team, to rise on their own merits - and undermines the whole system of voting.
The criteria for 'featured' selection remains vague, and the community is letting Product Hunt's CEO know how it feels on Twitter. His response to those who his team did not select to be featured, Ayyangar suggests: "Build better products."
Product Hunt Is No Longer Based on Votes
Ask HN: What's the best charting library for customer-facing dashboards?
Done some research and think chart.js seems like a great option. D3 seems powerful but might be complicated. Looking for simple + powerful, but maybe these are mutually exclusive... any advice?
Ask HN: Are any embedded BI tools good?
I've spoken to a bunch of people who use BI tools to embed analytics into their apps with an iframe. Nobody seems to like what they get despite some big players (PowerBI from Microsoft, Looker from Google, Tableau from Salesforce, Metabase etc. etc.) -- (Full disclosure: our team working on a solution to this)
I would question whether the 'ad-free' element of the strategy is potentially only a very small and ultimately insignificant weight in the perceived value of your tool vs others and might not be as impactful as you'd think -- if you deliver enough value for people not to care about having to ignore ads (which ppl are very, very good at these days) then they will confidently ignore the ads and find the value (e.g. academic referencing tools, wetransfer, {filetype}-to-{filetype} convertors)
Headless Tool Is 'Embedded Analytics Solution of the Year'
Do you think a best of both worlds solution would be valuable? (even if not immediately obvious how it could be possible!)
Say you wanted to build Stripes new analytics [1] you'd need to build those yourself with all the subcomponents and layout within each component to have your own style and native feel. The percentage increase subcomponent alone for example will have a bunch of it's own properties (colour, size, shading, edges, race conditions, position within parent component, etc.) AND will have a specific data request to pull it back.
So I guess the question is, does it matter if it looks like your platform or not?
Do you think a charting library is enough of a solution? As I understand you would still be required to do all the heavy lifting I mentioned above of building analytics from scratch, save for giving you a head start on the components themselves - right?
A analytics experience that A) looks like a nicely integrated part of our platform and, B) which doesn't force us to spend millions of developer hours, user feedback, etc to get it working
This I think would be an 'ideal solution' - if we could achieve that with what we're building do you think it would be useful or would there be more problems you'd foresee?
On the topic of sticking to the things you're good at. Would you be interested in a solution that allowed you all the flexibility to build a fully-native-looking experience for your customers whilst handling things like building components, localisation, and all of the boring bits for you?
Ask HN: Has anyone found a great solution for building analytics in your app?
It seems there are generally only two (imperfect) options for building analytics in your app:- either use a BI tool/out-of-the-box tool and embed an iframe (giving you very limited control and flexibility over the components & styling)- or build it yourself which allows you to make it look fully native, but turns out to be quite a heavy undertaking when you factor in...