to add detail: a major chromium implementation with the largest global user 
base on mobile, *does not support extensions*; behind all of its peers.

given this limitation, it strikes me as very important to get IWA onto 
chromium / mobile -- although I'm not sure this comment is on-topic as 
blink isn't opinionated. + I can only imagine the 'Jerry vs Anil' battles 
happening internally at these organizations. 

so if possible please keep us in the loop on IWA-install / discovery design 
docs so the community can try to replicate them on mobile -- if there's 
interest. 

🙏




On Thursday, September 7, 2023 at 10:36:20 AM UTC-4 polyset wrote:

> On Tuesday, August 29, 2023 at 1:22:35 PM UTC-4 rei...@chromium.org wrote:
>
> Supporting Android is not on our near-term roadmap
>
>
>
> after digging into the following working-groups: TWA, Payment Handler API, 
> and the Digital Goods API I believe there is a path for IWA on mobile; yet 
> due to security concerns from the community (especially mozilla) it will 
> likely need to be wrapped in a TWA. Unfortunately, when using a devx lens 
> this would be a step backwards. Developers want to develop on a platform 
> freely available to everyone. That platform is the web. When we require 
> them to juggle myriad tools (e.g., trusted-web-activity, bubblewrap, 
> play-store, CustomTabsIntent) to do something simple (i.e., socket()), they 
> will look elsewhere.
>
> I do want to point out the irony of our situation: on *mobile*, the 
> platform soon to be used by every human on the planet, will not have IWAs! 
> However I do understand and appreciate how we got here and why we don't (or 
> won't) have it. Onward with desktop IWAs!
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/25420925-7dbf-4ceb-8720-ca1de6d7f9f6n%40chromium.org.

Reply via email to