We want to build in-app reporting/analytics for our customers, but we don't want to use an out-of-the-box solution as we care a lot about look and feel. Has anybody had success in building in-app reporting themselves without it becoming a mess (never ending list of new features)? Any learnings you can share?
fwiw ... you <i>might</i> be "successful" doing what you're proposing (if you choose a tiny feature set, and discard everything else everyone asks you for)<p>...but the <i>reason</i> "out-of-the-box solutions" exist is because other folks have <i>already</i> spent the millions of developer hours, user feedback, etc to get it <i>working</i> :)<p>Several years ago I worked for a company (filled with seasoned, smart, great devs) that tried to in-house their own reporting tool<p>They quit and migrated to Crystal Reports because integrating an existing tool was worlds cheaper/faster than trying to do it all themselves<p>Later they migrated to BIRT because of CR limitations<p>And did another migration a couple years after that (I forget now to what tool)<p>The only drawback from a end-user perspective of those migrations were that reports couldn't be automigrated between reporting platforms
It sounds like you only want to build the frontend yourselves? You could take a look at Cube[1] which will probably work fine as a backend for your in-app reporting.<p>[1] <a href="https://cube.dev/" rel="nofollow">https://cube.dev/</a>