• Subscribe
    1. Discussions
    2. Upgrading the Web platform for next-gen applications

    Upgrading the Web platform for next-gen applications

    DoÄŸa Armangil
    9 replies
    Hello Product Hunt, I'm a software engineer and a software entrepreneur hailing from Geneva 🇨🇭. My quest to bring a Web-related deep-tech invention to market has brought me here. True story: There are things that applications can't do on the web, and I first noticed that when I tried to implement a web-based desktop system as an alternative to remote desktop solutions such as VNC. In hindsight it's obvious that the root cause was the Web being primarily a content platform, and not an application platform. So here I am, a couple of light-bulb moments and a patent and an award later, with a commercial-grade Frontend-Platform-as-a-Service offering: Qworum.net. My main target to begin with is business applications, both internal and SaaS. I'm launching Qworum on PH on Sept 13th. You're all invited!

    Replies

    Marina K
    Generated Photos
    Generated Photos
    Have a great launch, Doğa! I'll be there 🙂
    Share
    Marina K
    Generated Photos
    Generated Photos
    @doga_armangil Thank you, I like corrections. So it should be "Türk", right? Lunacy was actually a product of a company I used to work for, but I can tell someone there to fix it)
    Share
    Alexander William Hawkins
    Great question! I'm excited to try out the new features and see how they improve web app development. Wishing you all the best with the launch, Doga! Let us know how we can best leverage the platform upgrades.
    Share
    DoÄŸa Armangil
    @alexanderwilliamhawkins Thanks, right now what you get with Qworum is this: * distributed web applications (yes, Qworum manages to overcome the Web's same origin policy in a way that's secure!), and * a new API technology for interactive and composable APIs. Qworum APIs are much easier to call than REST etc. You can try Qworum right now. Local development is free, and you can start with this boilerplate I've published on 1000.tools: https://1000.tools/qworum-boiler... Feel free to let me know how it goes.
    Share
    Olivia Rose Thompson
    Awesome idea, Doga! Upgrading the web for next-gen use cases is so crucial. Have you checked out some of the latest web component frameworks like Lit and Stencil? They make it way easier to build fast, modern web apps while leveraging web standards. Rooting for your success with this - keep pushing the web forward! 💪
    Share
    DoÄŸa Armangil
    @lucasbenjaminfoster1 Thanks Olivia. As long as there are unsolved problems there is room for innovation. About Lit etc: I think web components are great, they make HTML much more readable, so I've done some "bare-metal" web components programming in the past without using any framework, just to see how things are working. But in a production site I'd build on an existing web components suite such as Lion, Material, Vaadin etc rather than building my own suite with Lit, Stencil etc. Are web components an alternative to Qworum? I'd say no, because Qworum is improving the Web platform itself, so what happens in a web page is largely orthogonal to what Qworum is doing. I wonder if people are using web components much these days, any opinions?
    Share
    Jason Matthew Lewis
    Congrats on the launch Doga! Web platform upgrades are definitely needed to keep up with the latest application innovations. Are you leveraging any cutting-edge tech like WebAssembly, WebGPU, or advanced APIs to enable next-gen features and performance? Super curious to learn more about your approach!
    Share
    DoÄŸa Armangil
    @jasonmatthewlewis Thanks. To me it's a matter of webapps keeping up with Web platform innovations rather than the reverse. What Qworum is about: Think of it as a new browser runtime that complements the JS runtime. How is Qworum different? Well, for one thing the Qworum runtime is attached to browser tabs rather than individual web pages as the JS runtime does. What happens in a browser tab then is essentially a sequential execution that spans web pages. In terms of WebAssembly etc: Qworum is implemented as a browser extension, and I don't (yet) use those technologies. The good news is, for webdevs not much will change: Qworum applications and APIs are built using the same technologies as before: HTML, CSS, JS (and WebAssembly etc). About Qworum scripts: Qworum uses XML for its domain-specific language (used for linking between services), but these scripts can be generated through JS as well, so XML is optional. OK, that was too much novelty :). Feel free to browse the extensive documentation and codebase I've written, and, of course, AMA.
    Share