Who designed this site? Readability is very poor. 8px font size for the 'pre-order' button, really?
And the contrast ratio is pretty low too.
Please, don't hire designers who just care about the graphic design aspect and making it look beautiful, but a pain to use, i.e. totally neglect usability.
I was hoping for a bit more in-depth material - allowing the experts to explore their topics a bit more and potentially talking about potential solutions? Where is the call to action for the viewer? What now?
It's good for non-technical folks to watch, but nothing really new since the 'Humans need not apply' 15 min documentary [0]
Actually, yes! All the parts of our site which are made in Pagedraw are fully cross-browser supported. That includes our landing page, dashboard, and parts of our editor.
Based on the feedback in this thread we're going to bump up the priority of this concern. Getting this kind of feedback is why we're doing this launch thread, so we really appreciate it.
I just tried spoofing my user-agent with Firefox, editor and preview worked but the designer was pretty broken. It seems Firefox and Chrome still have slightly different ideas about how layout is supposed to work, would be curious to hear what the differences are.
Super excited for the Figma + React-native support, I think ~20% of my time this past month was converting our designer's figma sketches into react native!
It was tough for us, because we're big believers in the standards-based web. We 100% promise that all the code we generate works across all browsers.
Our editor was almost electron-only, but felt it was better to launch with Chrome + Electron than just Electron. Our editor isn't a normal webpage; it's doing all kinds of crazy nonstandard things webpages shouldn't do. It's only in the browser at all so we can re-use a web engine as our editor's rendering engine, since we occasionally show you snippets of compiled code.
I'm personally really sorry as an engineer that we don't support Firefox, Safari, and other browsers yet. It's on our roadmap :)
- until recently, there wasn't a universal cross-browser API for pinch zoom support. Not sure if that's still the case.
- we do a lot of work with the selection/focus browser API, which doesn't always work the same / have the same APIs
- until recently, Firefox had a different opinion about where an outline should go wrt positon:absolute children
...and what seems like a million more little things. We decided it was more practical to do Chrome + Electron (basically the same) than try to cover every browser where the standards don't exist or aren't met, since we're touching a lot of surface area and weird corners of the browser.
Thanks. I think it’s a good decision, it seems like a classic example of needing to recognize sometimes going against conventional wisdom makes the most sense given particular circumstances, like gaining critical mass in a start up. As to where the right decision might be different for a later stage company.
So you seem really successful and financially sorted, but yet 'life has become hell' and you feel you have to fight to survive? Do you mean financially?
