3 ms·
> It's really hard to beat an embedded browser if you're doing a desktop GUI app. You could also just make it a website and stop there unless there is some nat
by bob1029 5y ago
> It's really hard to beat an embedded browser if you're doing a desktop GUI app.
You could also just make it a website and stop there unless there is some native hook you absolutely cannot manage via HTML5.
We started our product as a mobile app because of concerns over being able to access native device capabilities, but we have since reached a point where native doesn't make much sense compared to the amount of pain and suffering it causes us. Just the codesign process for iOS alone is not really worth the price of admission. This isn't even scratching the surface of xcode and the nightmare that is that ecosystem.
The only "native" thing we really need is the camera, and we have discovered a few reasonable shims for this particular concern (i.e. upload photo as a file).
- kbenson 5y agoIs the idea in a case like this to go full website, or use something like React/Vue to build a site that's just JS+HTML front end and API calls, and then ship a shim of an app which has a webview and the JS+HTML locally, and makes the same network API calls? Then it seems like the build process for native could be just about completely automated or at least reduced to it's basest components, and it's just dealing with App stores. Is this a normal thing that's already done? As is probably obvious, I'm not a front end or app developer.
- bob1029 5y agoOur long term goal is to go all-in on server-side rendered UI. For reference, we use Blazor server-side today and still feel this is still not extreme enough for us. What I would like to see is something where all browser events are piped to our server and we send basic WebGL draw commands back to the client. This would give us pixel-perfect control over how the application presents on any device without worrying about a particular vendor's quirks. Everyone's implementation of a web browser is a little different, but when you get down to the primitive behavior of basic WebGL/canvas usages, the consistency is very strong across all platforms. In order to accomplish this, the server would need to know about each clients' viewport dimensions, etc., so its not like its a free lunch on system resources. This is more about total control and maximum security.
- mwcampbell 5y ago> What I would like to see is something where all browser events are piped to our server and we send basic WebGL draw commands back to the client. Do you have a plan for also handling accessibility if you go in this direction?
- bob1029 5y ago> Do you have a plan for also handling accessibility if you go in this direction? It is something I would certainly consider after meeting the most urgent objectives. There is no reason I couldn't consider offering alternative views for certain users which contain things like high-contrast or screen-reader enhancements. The initial scope of this work would be for a privately-used B2B application. Accessibility in this context would be driven by our business customers' specific requirements. That said, providing accessibility is more of a business/application problem than a UI framework problem in my opinion.
- eropple 5y agoSo from where I sit, and mind you I'm not claiming to be perfect about accessibility but I spend a good bit of time thinking about it, this answer gives me shivers. 'Cause like: > It is something I would certainly consider after meeting the most urgent objectives. In practice, this is pronounced "no." > That said, providing accessibility is more of a business/application problem than a UI framework problem in my opinion. In practice, this is pronounced "I don't care". An application cannot describe "a button with the caption of 'OK'" without a UI framework that can and does tell it that there is a button, that it has a caption, and what that caption is. To be honest, accessibility is a team effort from everyone and things are already bad enough without actively making them worse.
- mwcampbell 5y ago> In practice, this is pronounced "I don't care". I appreciate that you're taking a stand for accessibility, but IMO, that kind of statement just adds to the shrillness of so much of our online discourse. We can discuss the pros and cons of various approaches to UI, and what it takes to make accessibility practical, without venturing into the topic of whether a developer cares about accessibility, which is likely to just make them defensive.