It's an optional step for hosted apps (it's optional for packaged apps as well). The goal is to help developers avoid users from installing their apps if it's not going to work on the users' devices. The app profile is honors system, and the incentive is to help users avoid a bad experience.
> I don't see how this will work in multi-device or pushing from desktop > to device environments if you have no platform support. I can't see how it will work with those features either, but I also haven't seen any of the work that the platform has done. We should probably have a conversation about how these features will work with our (and other) marketplaces. ----- Original Message ----- From: "Fabrice Desre" <[email protected]> To: "Matt Basta" <[email protected]> Cc: "Travis Choma" <[email protected]>, [email protected], "Mounir Lamouri" <[email protected]> Sent: Friday, May 24, 2013 11:46:25 AM Subject: Re: API for editing existing app installations On 05/24/2013 11:40 AM, Matt Basta wrote: > When an app is submitted, we (will soon) ask the developer which > APIs/features their app absolutely requires, with the list pre-populated with > smart guesses through the magic of static analysis. Developers can update the > app profile when they upload a new version. Reviewers will also soon have > tools to inspect the profile. But that's only for packaged apps, right? Hosted app can change their required features at will without looping in the marketplace, so that seems useless for them. > We then can calculate whether a device (based on which features it has) is > compatible with an app (based on which features the developer says it > requires). I don't see how this will work in multi-device or pushing from desktop to device environments if you have no platform support. Fabrice -- Fabrice Desré b2g team Mozilla Corporation _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
