canmove, Confirmed users
457
edits
Services/Sync/Features/Addon Sync: Difference between revisions
Jump to navigation
Jump to search
Services/Sync/Features/Addon Sync (view source)
Revision as of 19:34, 2 September 2011
, 2 September 2011no edit summary
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
|Feature version=TBD | |Feature version=TBD | ||
|Feature health=Blocked | |Feature health=Blocked | ||
|Feature status note= | |Feature status note=Page has been updated. Open item is UX flow, if any for when add-ons are updated due to sync. | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
| Line 20: | Line 20: | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature open issues and risks=<table border=1> | |Feature open issues and risks=<table border=1> | ||
<tr bgcolor="# | <tr valign="top" bgcolor="#AAAAAA"> | ||
< | <td>Issue/Risk</td> | ||
< | <td>Status</td> | ||
</tr> | </tr> | ||
<tr> | <tr valign="top"> | ||
<td>Is this only for desktop to desktop add-on syncing? Like AdBlock Plus. If this works across devices great! If not the priority is first to get desktop to desktop working and then worry about mobile. I need to understand the work involved.</td> | <td>Is this only for desktop to desktop add-on syncing? Like AdBlock Plus. If this works across devices great! If not the priority is first to get desktop to desktop working and then worry about mobile. I need to understand the work involved. | ||
</td> | |||
<td>This will work between add-ons belonging to the same application ID (e.g. desktop, Fennec). The system will be forward compatible, so if we want to try enabling syncing across applications of different IDs, we can do that easily.</td> | <td>This will work between add-ons belonging to the same application ID (e.g. desktop, Fennec). The system will be forward compatible, so if we want to try enabling syncing across applications of different IDs, we can do that easily.</td> | ||
</tr> | </tr> | ||
<tr> | <tr valign="top"> | ||
<td> | <td> | ||
Why does Sync need to be used for updating | Why does Sync need to be used for updating add-ons? Would the user not be prompted to update the add-on through the browser? | ||
</td> | </td> | ||
<td> | <td> | ||
| Line 37: | Line 38: | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr valign="top"> | |||
<tr> | |||
<td> | <td> | ||
Do we need some prompts or feedback when add-ons are synced, at all? | Do we need some prompts or feedback when add-ons are synced, at all? | ||
| Line 46: | Line 46: | ||
</td> | </td> | ||
</tr> | </tr> | ||
<tr valign="top"> | |||
<tr> | |||
<td> | <td> | ||
Are there any problems with large sets of add-on state being updated at once? Say the user has not used a device for a while and they use it again and a whole bunch of add-ons need to be updated. | Are there any problems with large sets of add-on state being updated at once? Say the user has not used a device for a while and they use it again and a whole bunch of add-ons need to be updated. | ||