introducing in Hex: Generative Data Apps backed by code, so you can build anything you want! a dashboard, an editorial, a customer prezo - you name it, you can build it 💜 integrated with your data team's context + built w/ governance, security and observability top of mind

@_hex_tech going to build a dashboard for how many spindrifts i consume at olivia's parties

@_hex_tech its so up and to the right i can never buy enough

this is wonderful — played with it all morning. Quick feedback: - reusable component support and tailwind / shadcn + - Component shape feels dated — modern JSX please, not h = React.createElement(...)? - Per-user state + write-backs (budget/forecasting apps need this so much) - Unclear how this coexists with classic apps — can I embed notebook components on the app direcly? - Code editor needs love! - Multiple apps per project to enable per user slices? Overall a dream come true, well done @_hex_tech 🙌 (caveat: haven't read the docs, just vibed — apologies if this exists)

great feedback, shared with the team! Keep it coming! & glad it was intuitive enough no doc reading needed 😄 re coexists with classic apps- you can choose between either classic or the new generated app, and swap between the two but there currently isn’t a way to embed any cells

A few more reflections: Many companies are struggling with this new type of debt -> users excited with making data apps in <insert chat app>... only to learn they are "bodies without a soul", "car without an engine",... meaning no data access, no data/state persistence, no path to production or refreshing, no sharing, important docs "saved" inside the thread, etc With this launch, Hex earns right to be the place for that creativity to come to life and avoid "html dashboard slop". Some of my points above are a path to that anchor but specially reusability and state management, I'd highlight as important ones. How I'd like to see some of this solved: - opinionated state management on the tsx files like a global you can trust " and that your agent knows well... like a hex management zustand or something. - That state needs to be aware of what the user is seeing. For example a comment on a filter needs to know why the user made the comment. - You probably need some global also for calling APIs and stuff or some clarity about the "backendish" execution role of cells and how they interact with the frontendish nature of the (beta) app. Is it a fetch? is it a server action? what is it? Maybe if you guys do a write up on how you're thinking of the execution model and future of this would be great. Cheers

@_hex_tech brb going back through all the old apps i've ever made and regenerating them as street fighter loading screens

read more about it

@_hex_tech Brb making all my internal dashboards Barbie themed 💗

@_hex_tech BUT ACTUALLY YOU SHOULD, its so delightful 🩷

@_hex_tech #GirlsWhoCode

@_hex_tech Really really cool

@_hex_tech This can replace a whole category. Can generative data apps be served directly to an agent via CLI or MCP in a non hex surface?

@_hex_tech by served to you mean generated or used/referenced?

@_hex_tech WHOA COOL

@_hex_tech THANK YOU!!!

@_hex_tech this is super lit

@_hex_tech when do we get u back on hex!!!!

@_hex_tech sooner than you know!!

@_hex_tech these dashboard are sooo good!

@_hex_tech thank you Kate!!! It’s been so fun to build

@_hex_tech So goood!!

@_hex_tech can’t wait to hear you feedback!!

@_hex_tech makes me want to play with data!!

@_hex_tech DO IT JENNY I DARE U

@_hex_tech so amazing 😭😭😭

@_hex_tech Tell me what you think devang!!!!!!!

@_hex_tech Have I ever wanted to theme all my dashboards with ridiculous fantasy graphics? … yes

@_hex_tech Excited for this!

@_hex_tech hypeeeee 🥰