Marketplace/getFeature: Difference between revisions

Jump to navigation Jump to search
WIP
m (renamed Overview to Implementation)
(WIP)
Line 43: Line 43:
The marketplace that is shipping with 2.0 doesn't have permission ("feature-detection") to use hasFeature/getFeature, so we need to update the package regardless of the "real" vs "iframed" packaged app.
The marketplace that is shipping with 2.0 doesn't have permission ("feature-detection") to use hasFeature/getFeature, so we need to update the package regardless of the "real" vs "iframed" packaged app.


= Development needed =
= Development Roadmap =
 
== Initial release (WMW/Hello, Q4 2014) ==
'''For getFeature itself:'''
'''For getFeature itself:'''
# add a buchet for 512MB RAM minimum
# add a buchet for 512MB RAM minimum
Line 53: Line 55:
# while we aren't attempting to force install (or any other clickable action from the update notification) for this project, if there is a permission that needs to be requested for it, we should add that now so it's there when we need it later
# while we aren't attempting to force install (or any other clickable action from the update notification) for this project, if there is a permission that needs to be requested for it, we should add that now so it's there when we need it later


== Issues ==
== Full release (Q1/Q2 2015) ==
We will implement feature detection using <code>hasFeature</code> and <code>getFeature</code> APIs where possible; we will resort to manual checks where not possible. For devices that do not support those APIs -- whether they are on older versions of the Marketplace or Gaia -- we will simply apply a limited feature profile.
 
This means that any marketplace originally shipped on 2.1 or lower, or any marketplace running on a version less than 1.4 will be checked for feature compatibility in a very limited capacity.
 
== Known Issues ==
 
=== getFeature ===
=== getFeature ===
# There is an existing issue with getFeature() in that it will test for the existence of the API, but this could be out of sync with the actual hardware.
# There is an existing issue with getFeature() in that it will test for the existence of the API, but this could be out of sync with the actual hardware.
=== Updating the Marketplace ===
=== Updating the Marketplace ===
# We cannot update the marketplace app on 1.1 ({{Bugzilla|962524}})
# We cannot update the marketplace app on 1.1 ({{Bugzilla|962524}})
Line 76: Line 85:
# If it takes so much time to QA that we CAN get this done in time, but we could also be a real packaged app by then, there is less point to pursuing the packaged iframe.
# If it takes so much time to QA that we CAN get this done in time, but we could also be a real packaged app by then, there is less point to pursuing the packaged iframe.


After consulting with QA, we decided:
= Bugs =
# to implement getFeature initially only for WMW & Hello (thereby minimizing what needs to be tested)
 
# ...using the current packaged iframe
Tracking bug: {{Bugzilla|}}.
# ...and use this opportunity to introduce update availability notification
 
<bugzilla>
{ "blocks": [""], "status": ["UNCONFIRMED", "ASSIGNED", "NEW", "REOPENED"] }
</bugzilla>


= Future product feature phases =
= Future product feature phases =
Confirmed users
746

edits

Navigation menu