Re: [w3ctag/design-reviews] Question: Review manifest-first Web Install API (Issue #1245)

marcoscaceres left a comment (w3ctag/design-reviews#1245)

There seems to be some confusion between browsers as products and browser engines. WebKit, an engine and open source project, is not Safari: a web browser product that makes use of the webkit engine. Smart Banners are a product decision.

Product decisions are outside the scope of the discussion. 

> Do “Smart App Banners” belong in web pages at all? Almost certainly not.

I don't think Apple ever proposed to standardize Smart Banner, AFIK. That's a fundamental difference. No one is advocating for a Smart Banners web standard.

@slightlyoff, you've, again, completely missed the point of the WebKit feedback or are willfully choosing not to engage with the main point. Let me ask it in simple terms: do **users** want install buttons on their pages at all? Chrome's own data seems to suggest that users **do not** want this stuff in their web pages, even if developers think it's a fabulous idea - just like users probably wouldn't want a `<button>bookmark this page</button>`. That's why WebKit's position is: users who want to install an app can just use the browser's UI.

Could browsers do better improving the install/add to home screen UX? Sure. 

Are developers going to do better than browsers? that's literally the question. And, given this affordance, is there a risk that the feature could be misused to nag users to install precisely because it grants the app more capabilities? Even if well-intentioned, it fundamentally changes the incentives of developers. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1245#issuecomment-5261702066
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1245/5261702066@github.com>