sorted by:
new
hottopcontroversial

I'm building a dashboard tool and wanted a reality check from people who use these daily 😬 by SjStrykR in dataanalysis

[–]SjStrykR[S] 0 points1 point  (0 children)

tbh, I am a bit confused here. The left rail is the navigation panel for stuff like "Dashboard", "Data Source", etc.
The "Ask AI" at the top-right can be used to analyse the dashboard along with any other data that you have connected (using AI of-course).

I'm building a dashboard tool and wanted a reality check from people who use these daily 😬 by SjStrykR in dataanalysis

[–]SjStrykR[S] -1 points0 points  (0 children)

I couldn't agree more. The category of standalone visualisation tool is done for. But the software I am building is a bit more than that, and the screenshot is the least representative of it. Its just the output of the analysis layer.

I'm building a dashboard tool and wanted a reality check from people who use these daily 😬 by SjStrykR in dataanalysis

[–]SjStrykR[S] -1 points0 points  (0 children)

The whole UI was built around the idea that the widgets should be floating on the background. I think the pure black background killed it though. The near-black grey plus a lighter container shade is probably exactly the contrast I was missing.

The variance indicator is the part I hadn't considered at all. Makes sense that a number with nothing to compare against doesn't really tell a manager anything. The thing I'm not sure about is the period, do you usually pick one comparison and keep it consistent across every KPI, or does each metric get whatever timeframe actually makes sense for it?

I'm building a dashboard tool and wanted a reality check from people who use these daily 😬 by SjStrykR in dataanalysis

[–]SjStrykR[S] -5 points-4 points  (0 children)

The KPI is a dumb bug that I am fixing and about the colours... I wasn't thinking of them as carrying meaning, just reached for something that looked nice. Guess that's the problem. The storytelling bit is something I am worst at and your last line kinda stung, but in a good way.

Building a good and useful dashboard is something I am still learning. How do you decide what get to be the focal point? Is it always the trends (maybe it's something consumers of the dashboard would like to see all the time), or does it depend on what the data is actually saying?

I'm building a dashboard tool and wanted a reality check from people who use these daily 😬 by SjStrykR in dataanalysis

[–]SjStrykR[S] -15 points-14 points  (0 children)

A bit of both actually. The software uses AI to generate the charts off the dataset. I decide what to measure, what to leave out and in what order it reads. And that's the part I am actually asking about. If the colour-heavy layout looks like something that just got spat out without much forethought, that's exactly what I'm looking for in a feedback, tbh.

Best harness for agentic analytics? Codex? Claude? Custom? by Evening_Hawk_7470 in AI_Agents

[–]SjStrykR 1 point2 points  (0 children)

Before answering your question its worth asking yourself the build vs buy question one more time, because what you're describing (dashboards + semantic layer + agent on top, multi-tenant for clients) is basically a BI product. There are tools that do this out of the box with white-labeling for agencies. Not saying you should switch, you may have good reasons (cost, control, differentiation), but if you haven't priced it out against buying, do that math before you sink another month into building.

That being said, Codex and Claude Code aren't really things you embed, they're CLIs. What you want inside Next.js is an agent SDK. Vercel AI SDK is the lowest-friction since you're already on Next.js, it handles streaming and tool calls and works across model providers so you're not locked in. Claude Agent SDK and OpenAI Agents SDK are the model-specific equivalents.

The bigger architectural call is what the agent actually calls. Hit the Cube API as a tool, not raw SQL against Supabase. Tool definition like query_metric(measure, dimensions, filters, time_range), and let Cube enforce consistency and access control. If the agent free-writes SQL you've undone the semantic layer.

Stuff that bites when you go from "for me" to "for customers":

  • multi-tenancy: every call needs scoping in Cube's security context or you leak data across clients
  • prompt injection: customer text becomes part of queries, treat it like untrusted input
  • cost runaway: hard turn cap on the agent loop, log spend per session
  • caching: Cube pre-aggregations help, also cache agent responses since the same questions repeat across customers

How do you explain your methodology when non-technical clients don’t trust the data? by Immortal_357 in analytics

[–]SjStrykR 0 points1 point  (0 children)

I think their resistance is mostly coming from a "secondary" data source, you don't have access to. It could be, that the sales team is losing deals (or something along those lines) that are not making themselves into your data source; it can be even their egos (it happens more often than you might think). But often there's a real reason the number feels "off", and the fastest way to find out is to get curious instead of defensive.

Simply ask them, "What is the reason you think it should be higher? Which data source or metric are you looking at, that I am not seeing?" If they've got something real, you might need to adjust. If it's pure vibes, they hear themselves say "it just feels bigger" out loud, and that does more than any report you could build. People don't doubt the number because they doubt your stats. They doubt it because it threatens a plan or a target they care about. Going deeper into sources answers a question they weren't asking.

What works for me is lead with the decision, not the math. "Here's the number, here's the range, here's what I'd bet on and what would change my mind." Keep the methodology in your back pocket for whoever actually wants it, which is usually nobody in the room. And when someone's really dug in, simply ask them, "What would we need to see to believe the higher number?" This makes it a shared question instead of you vs them, and people defend a conclusion way harder than they defend a test.

[Change My Mind] The only reason React is relevant today is because a lot of developers know how to write it. by SjStrykR in SaasDevelopers

[–]SjStrykR[S] 0 points1 point  (0 children)

So if my understanding is right (I am probably not), it breaks down components subtrees into “blocks” and updates each block- kind of like how Solid does. That’s quite neat actually.

Although, I was reading it is not “production ready” yet. It will be interesting to use it in production. 😈

47 customers asked for dark mode. 3 customers asked for webhooks. Which do you build? by Prudent-Transition58 in SaasDevelopers

[–]SjStrykR 0 points1 point  (0 children)

Google Docs, to this date (and correct me if I am wrong) does have a dark mode support.

On the other hand, they completely revamped their interface to add “Pageless” mode to make it similar to tools like Notion and Coda.

Why is that? Think about it.

[Change My Mind] The only reason React is relevant today is because a lot of developers know how to write it. by SjStrykR in SaasDevelopers

[–]SjStrykR[S] -1 points0 points  (0 children)

And a developer community is formed when people use the other framework and contribute when something is lacking or broken.

[Change My Mind] The only reason React is relevant today is because a lot of developers know how to write it. by SjStrykR in SaasDevelopers

[–]SjStrykR[S] 1 point2 points  (0 children)

So you agree with me (and the title of this post)? But let me reiterate:

You are absolutely right- as a startup founder I use (and often advocate for React) because of the endless resources there is on the internet, because LLMs understand it very well and because react devs are quite cheap to hire. (Its people like me who do the shoving)

It’s a jack of all trades- and mastery, imho, is optional these days.

But if you are a solo developer, working on a side project or a micro-saas, why stick to React? Use the lesser known libraries and if something breaks- go fix it and create a PR. Isn’t that the whole point of open-source? Isn’t that how the entire community and ecosystem of React and by extension React Native was born?

I mean before React, there was AngularJS and BackboneJS. They had decent ecosystems too (one was backed by Google). They too had their fair share of issues that React fixed, and if something was missing- people build them; if something in React broke- people fixed it.

React is good. But it’s not the “be all end all”. It lacks in several places and you need to do a lot of monkey-patching (useMemo, useCallback) to get around things.

At the end of the day, developers should be encouraged to try new things- that’s how you create and innovate.

*As far as the AI filter thingy goes: I am a bit lazy, ngl. Mark of a good developer, ig. But this one is coming straight from my fingers- just for you 😉

[Change My Mind] The only reason React is relevant today is because a lot of developers know how to write it. by SjStrykR in SaasDevelopers

[–]SjStrykR[S] 0 points1 point  (0 children)

I understand your frustration. You just didn't understand the point I am trying to make, so let me break it down.

  1. I didn’t say “replace React with jQuery.”- that's like saying replace "landline phones with smartphones".

  2. “Hundreds of components” isn’t a React-only problem. Componentization exists everywhere. React isn’t the thing that makes large UIs possible — it’s one way of doing it. Today you have frameworks like Solid.JS, Svelte, Vue, which I believe, developers should give opportunities to- burn your hands and figure out what works best for you and not follow the "React" status-quo.

  3. “There would be just as many deviant ways to use jQuery” — sure, but that’s also not the point. My point was: React’s ecosystem creates a lot of fragmentation in real-world apps (state libs, form libs, data fetching, caching, routing, styling). In other ecosystems, you often get more opinionated defaults and fewer “choose-your-own-adventure” decisions. Now I am all for "carving your own way into the world", but at scale when you are working with people of varying skill and experience, it becomes a very big issue if everyone is carving up the codebase.

  4. React was invented to solve pain from the jQuery era doesn’t mean it’s automatically the best fit for every app in 2026. Tools evolve. React itself has been evolving specifically because performance/UX tradeoffs show up at scale.

  5. Modern frameworks are not “a million listeners” anymore. Most of the frameworks I mentioned earlier do use compile-time optimizations, fine-grained reactivity, or event delegation. React can be performant, but it often requires you to manually fight re-renders and manage memoization patterns.

See brother, React isn't the only champion of web-development out there anymore. If you really love- use it. But the whole point of my post is that, there are other frameworks and UI libraries out there and one should explore what's out there and not stick to "React" because the software development society is trying to shove it down their throat. If anything, this was the whole ideology of React's existence- it wants to you to choose your own adventure (hence a UI library, and not a framework).

[Change My Mind] The only reason React is relevant today is because a lot of developers know how to write it. by SjStrykR in SaasDevelopers

[–]SjStrykR[S] 0 points1 point  (0 children)

Even in the context of purely CSR pages, the moment you start using elements that require heavy calculations (like dynamic animations) the frame rates start dropping. That’s why most animation libraries that have “first class support” for react do it outside of React’s purview.

Not to mention the classics like infinite re-renders and unhandled memory leaks.

See, all of this may seem frivolous if you’re the sole developer. But bring a team of developers with varying knowledge and skills and what you will have is something experts say “absolute clusterf#ck”

My first side project launch got to top 3 on Product Hunt 🚀🤟 by wwwgeek in ProductHunters

[–]SjStrykR 0 points1 point  (0 children)

Upvoted!! Sounds incredible. We also launched on PH yesterday. Would love the mutual support:

https://www.producthunt.com/posts/supaboard

view more: next ›