Canmove, confirm
457
edits
Changes
no edit summary
{{FeatureStatus
|Feature name=Addon Sync
|Feature stage=DefinitionDesign
|Feature status=In progress
|Feature version=TBD
|Feature health=Blocked
|Feature status note=Page has been updated. Open Blocked by the open item is of UX flow, if any , for when add-ons are updated due to sync.
}}
{{FeatureTeam
<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.JA - Let's stick to same application ID for now. </td>
</tr>
<tr valign="top">
|Feature overview=Sync is a service to keep the Firefox experience consistent across multiple devices by ensuring user data is synced across various devices. This feature will enable add-ons to be synced across devices. Add-ons are small pieces of software that add new features or functionality to an installation of Firefox. Add-ons can augment Firefox with new features, foreign language dictionaries, or change its visual appearance. Through add-ons, you can customize Firefox to meet your needs and tastes.
Sync will ensure that add-ons are installed, uninstalled, updateddisabled, and enabled as they are changed on each clientfor the same application. This means that desktop to desktop add-ons will sync, and mobile to mobile add-ons will sync.|Feature users and use cases=; Desktop browser to browser add-on install
* A user has sync set up his work and home desktops
* He goes to AMO and installs an add-on on his work computer
; Non-impact on add-on manager metrics : The presence of Sync should not skew the metrics in the add-on manager and addons.mozilla.org. Currently, some APIs on the AddonManager upload metrics.
|Feature non-goals=;Syncing add-on information across different Application IDs ;Sync will not synchronize non-XPI add-ons such as plugins, lightweight themes, and search engines. Sync will also not synchronize add-ons installed outside of the currently running profile.
|Feature functional spec=The Addon Manager maintainers would like to see Sync support all add-on providers so as to not introduce 1st and 2nd class providers.
There are some interesting implications for the design proposed above. AddonManager and providers - not Sync - would be responsible for the format of the records containing add-on metadata and this means the onus of ensuring forwards and backwards compatibility (since e.g. a version 9 client could receive a Sync record from a version 14 client and vice-versa) reside in the AddonManager and providers. This might be new territory for AddonManager and providers. Unfortunately, the alternative means lots of AddonManager-specific code in Sync (at best) or giving up provider agnostic add-on sync (at worst).
|Feature ux design=;May need some for giving the user feedback when an add-on is being updated due to sync.
}}
{{FeatureInfo
|Feature engineering team=Sync
}}
{{FeatureTeamStatus|Feature products notes=Cutting having sync update the add-ons since that mechanism is already a part of Firefox. I will follow up with FF folks to see if Sync does bring value. We can address it later. }}
Discussion notes from 2011-08-16:
