Developing on and for Chromebooks is a terrible experience
1–10 of 29 posts
Re: Developing on and for Chromebooks is a terrible experience
#2Member-only story, fyi
Re: Developing on and for Chromebooks is a terrible experience
#3I'm not sure what a ChromeOS developer writes, since the "native apps" are PWAs only.
The author mentions various driver-like things, such as a custom keyboard. Can such custom drivers be installed when not in Developer Mode? I see no mechanism to do so, nor any "ChromeOS app store" where I might download such things.
If you're a ChromeOS developer, where and how do you distribute your products?
Re: Developing on and for Chromebooks is a terrible experience
#4I'm not sure what a ChromeOS developer writes, since the "native apps" are PWAs only. The author mentions various driver-like things, such as a custom keyboard. Can such custom drivers be installed when not in Developer Mode? I see no mechanism to do so, nor any "ChromeOS app store" where I might download such things. If you're a ChromeOS developer, where and how do you distribute your products?
Author here.
App distribution is a major issue for the platform that I ran out of space to really talk about. Those driver-like things are largely extension APIs, but they were once the domain of the now deprecated "Chrome Apps." Both the Apps and Extensions are delivered via the Web Store, but I feel like there's a steady move to deprecate all system-customization on the platform.
If you want to use some non-optimized apps in a VM though, you can use the Gnome Software store or the Google Play Store.
Re: Developing on and for Chromebooks is a terrible experience
#5Member-only story, fyi
Re: Developing on and for Chromebooks is a terrible experience
#6Re: Developing on and for Chromebooks is a terrible experience
#7Re: Developing on and for Chromebooks is a terrible experience
#8Earlier quoted context omitted.
https://archive.is/tQgER
Oh man that leads me into an infinite Cloudflare captcha loop on my iPhone :-(
Re: Developing on and for Chromebooks is a terrible experience
#9I'm not sure what a ChromeOS developer writes, since the "native apps" are PWAs only. The author mentions various driver-like things, such as a custom keyboard. Can such custom drivers be installed when not in Developer Mode? I see no mechanism to do so, nor any "ChromeOS app store" where I might download such things. If you're a ChromeOS developer, where and how do you distribute your products?
There was "Portable Native Client" aka. PNaCl. Users can't ship PNaCl apps themselves anymore (atleast via the store) since "Chrome Apps" died, but if you open the Terminal on a Chromebook you'll notice it still says "loading PNaCl client" so they certainly still use it internally.
Re: Developing on and for Chromebooks is a terrible experience
#10I'm not sure what a ChromeOS developer writes, since the "native apps" are PWAs only. The author mentions various driver-like things, such as a custom keyboard. Can such custom drivers be installed when not in Developer Mode? I see no mechanism to do so, nor any "ChromeOS app store" where I might download such things. If you're a ChromeOS developer, where and how do you distribute your products?
Author here. App distribution is a major issue for the platform that I ran out of space to really talk about. Those driver-like things are largely extension APIs, but they were once the domain of the now deprecated "Chrome Apps." Both the Apps and Extensions are delivered via the Web Store, but I feel like there's a steady move to deprecate all system-customization on the platform. If you want to use some non-optimiz…
To clarify, you can run standard linux apps in a linux VM with seamless file, wayland and X11 passtrough ("crostini"). Even nested virtualization works.
And you can run android apps in a android VM.