I understand why early stage products don't list pricing (the least of which is that they are in flux) but it makes me sad when I see interesting products that don't give me pricing. I end up having to writeoff/ignore the product because I don't have the mental space to remember it without pricing. and these days ill never sign up for someone's newsletter if I can help it!
a) good new products: they know they don’t know their products value yet, so you can actually offer what it’s worth to you and they will accept that. b) bad products: it’s an extortion play and they will get what they can. solution: a) if you need their product buy it, and plan how to migrate away from it b)buy their stock and hope that not much people plan how to migrate away.
Hello, Dynaboard
11–20 of 49 posts
Re: Hello, Dynaboard
#12I understand why early stage products don't list pricing (the least of which is that they are in flux) but it makes me sad when I see interesting products that don't give me pricing. I end up having to writeoff/ignore the product because I don't have the mental space to remember it without pricing. and these days ill never sign up for someone's newsletter if I can help it!
Seeing "coming soon" and "enterprise" on the pricing page is a guaranteed pass from me (but not a permanent one).
Re: Hello, Dynaboard
#13Multiplayer: We used the YJS project (https://github.com/yjs/yjs) as the baseline for our multiplayer system. We created a thin harness around the client and ended up implementing our own server-side architecture to handle relaying between the various WebSocket servers. More on how we do this soon.
WebAssembly: Rather than running your custom code in an iframe, we run it inside a wasm-based sandbox, a compiled version of the QuickJS VM (yes, it's JS-in-JS). This approach gives you synchronous access to most of the DOM APIs without sacrificing safety. We do some fancy ES6 Proxy management to implement the FRP-like data binding system inside the VM. In production, the browser runs the project's precompiled bytecode. In the future, we plan to support other languages with a similar architecture (Python via Pyodide, Rust, Go, etc.).
Code editing: We use Monaco, the same editor that VS Code uses. We've had to create a handful of custom extensions, including a few custom language servers, to get it to be aware of the VM environment. I'm a vim-er so we will definitely have a vim mode.
Re: Hello, Dynaboard
#14Re: Hello, Dynaboard
#15I'm curious how this compares to AppGyver (https://www.appgyver.com) which was recently acquired by SAP. (I am not affiliated).
Re: Hello, Dynaboard
#16Why would someone choose this over Microsoft's Power Platform or Salesforce's platform? Interesting tool, but it seems like it doesn't have a clear audience in mind. The end user seems to be "everybody" and that's a hard sale to make.
Re: Hello, Dynaboard
#17Why would someone choose this over Microsoft's Power Platform or Salesforce's platform? Interesting tool, but it seems like it doesn't have a clear audience in mind. The end user seems to be "everybody" and that's a hard sale to make.
It's not only unclear at first glance who the audience is, but what the tool actually does. It seems like some kind of no-code tool at first, but then it mentions pair programming? I'm confused, and don't want to wade through a swamp of marketing text.
Re: Hello, Dynaboard
#18How realistic hosting on-premise / in a private cloud without breaking the bank is? The price is "contact us" right now. I sometimes need to develop applications where privacy and GDPR is critical.
The current pricing per developer/user is not announced and I see that as a risk for me. I have been priced out of Retool, they wanted more money than two good full-stack senior developers, so I would like to know if your product is going to make sense for me before I invest time and resources in it. I'm currently using AppSmith.
Re: Hello, Dynaboard
#19Why would someone choose this over Microsoft's Power Platform or Salesforce's platform? Interesting tool, but it seems like it doesn't have a clear audience in mind. The end user seems to be "everybody" and that's a hard sale to make.
It's not only unclear at first glance who the audience is, but what the tool actually does. It seems like some kind of no-code tool at first, but then it mentions pair programming? I'm confused, and don't want to wade through a swamp of marketing text.
We're building for early-stage technical teams and independent developers that want to reduce the iteration time on prototype -> production apps.
Re: Hello, Dynaboard
#20Nice landing page. Looks like you're missing a polyfill for ResizeObserver.