Hello HN !

I'm Florian, and I would like to share with you a project I've been working on over the past few months: Hyper Workspace.

Before working in tech, I have been in the finance industry for more than 10 years. During this time, I've experienced using Excel+VBA and Python notebooks as main interfaces, but never felt completely satisfied. Interfacing potentially complex and nested objects that you need to consume in your applications is still a pain. Modern browsers can offer much more in terms of UI / UX, especially when coupled with JSON data representation, but they require to write and deploy specific code, use a rendering library... and I believe there is a better way: JSON deserves a fully horizontal framework, abstracting web semantics, and filling the gap between data, views and behavior.

To this end, I've been trying to shape Hyper Workspace so that it can provide no-code tools to build Documents':

   - Fields: strongly typed, deeply nested and potentially recursive, data structures (inspired by Typescript).

   - Views: drag n' drop configuration of documents' pages (ie sub-objects): layout, fields, widgets, actions, graphs.

   - Methods: visual configuration of your "business logic" using a Domain Specific Language, plugged at every layer of your data structure, with an "object-oriented programming" philosophy. Builtin "Modules" can be used to add more functionalities.

You can build "standalone" Documents (like spreadsheets) but also Collections where Records share the same Schema, like a NoSQL version of Airtable. Unstructured data (pdf, images, audio, video) are stored as "Files" that can be linked inside Documents.

All this in a multi-desktops OS-looking environment. You will find a complete documentation inside your workspace.

So far, this is a purely local application that stores everything in your IndexedDB. It can be installed locally (PWA) and will then work completely offline. No account required and nothing leaves your device.

This is more the early stage of a framework than a complete product, but I hope it can shed a light on a potential new way to "configure" interfaces or even workflows, given that Documents can be seen as stateful representations of business processes. Builtin "Modules" are the key to extending the framework's capabilities: calling APIs, using AI agents to structure or query documents, or even take action...

I'd love to read your feedbacks, questions and ideas on it, and see together what could make it useful for you !

Thanks ! Florian