> If you purely look at it from the "most value for most users" perspective, Fenix extensions are a great success.
Except for the part where so many extensions that already have the needed APIs implemented still can't be installed.
Changing that setting would move the needle with minimal developer effort.
> But it's not clear that "mobile-browser-as-a-developer-platform" is a sustainable long-term pitch for an organization as small and as resource constrained as Mozilla.
They were trying to make an entire OS, and now they can't keep the browser shell updated?
There's correction and then there's overcorrection.
Also I want my desktop and phone browser to work together well, so failure to make the phone work pushes me away from everything.
Except for the part where so many extensions that already have the needed APIs implemented still can't be installed.
Changing that setting would move the needle with minimal developer effort.
> But it's not clear that "mobile-browser-as-a-developer-platform" is a sustainable long-term pitch for an organization as small and as resource constrained as Mozilla.
They were trying to make an entire OS, and now they can't keep the browser shell updated?
There's correction and then there's overcorrection.
Also I want my desktop and phone browser to work together well, so failure to make the phone work pushes me away from everything.