</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.
<br/>JA - Let's stick to same application ID for now.
</td>
</tr>
<td>
It doesn't need to be used for updating add-ons. This is just an easy win. It can easily be postponed to after the initial release.
<br/>JA - I would rather postpone because I do not really see the value add since the user already has a way to do this. If this solves a pain point the user has with the current update process of add-ons maybe we can talk to the add-on folks to have them solve it.
</td>
</tr>
* When he goes home and starts his Firefox browser this add-on will enable itself and not show up in the add-on tab
;Not sure about the update case
|Feature dependencies=; Sync GUID added to XPI Provider : Sync requires non-deterministic IDs to be affiliated with synchronized records. XPI add-ons currently don't have a suitable ID so once will need to be created.
|Feature requirements=*When a user installs an add-on, the add-on will be installed on all the user's devices connected with Sync.