This is really nice, specially the pdf report generation.

I feel very moronic making a dashboard for any products now. Enterprise customers prefer you integrate into their ERPs anyway.

I think we lost the plot as an industry, I've always advocated for having a read only database connection to be available for your customers to make their own visualisations. This should've been the standard 10 years ago and it's case is only stronger in this age of LLMs.

We get so involved with our products we forget that our customers are humans too. Nobody wants another account to manage or remember. Analytics and alerts should be push based, configurable reports should get auto generated and sent to your inbox, alerts should be pushed via notifications or emails and customers should have an option to build their own dashboard with something like this.

Sane defaults make sense but location matters just as much.

▲

jorin 6 minutes ago | parent | next [-]

hi, dev building Shaper here. I agree re sending reports vs dashboards. Many users use Shaper mostly as UI to filter data and then download a pdf, png or csv file to use elsewhere. We are also currently working on functionality to send out those files directly as messages using Shaper's task feature.

▲

mitjam 3 hours ago | parent | prev | next [-]

1999-2000, the company I worked with gave a smallish number of key users full read rights to the SAP minus HR, briefly after introducing SAP to the global supply chain of that company. The key users came from all orgs using SAP, basically every department had one or two key users.

I was part of this and "saw the light". We had such a great visibility into all the processes, it was unreal. It tremendously sped-up cross-org initiatives.

Today, I guess, only agents get that privilege.

▲

matsz 3 hours ago | parent | prev [-]

> I've always advocated for having a read only database connection to be available for your customers to make their own visualisations.

A layer on top of the database to account for auth/etc. would be necessary anyways. Could be achieved to some degree with views, but I'd prefer an approach where you choose the publicly available data explicitly.

GraphQL almost delivered on that dream. Something more opinionated would've been much better, though.

	▲	written-beyond 32 minutes ago \| parent [-]
		That's exactly what I meant. It's a specific replica instance with it's own security etc. but not necessarily a separate API you try to integrate too. APIs can stay for writes, but for reads you have the db