Features/Services/KeepBookmarksInSyncWithChrome

Please use "Edit with form" above to edit this page.

Status

Allways Keep Bookmarks In Sync With Chrome
Stage	Feature Inbox
Status	`
Release target	`
Health	OK
Status note	`

Team

Product manager	`
Directly Responsible Individual	`
Lead engineer	`
Security lead	`
Privacy lead	`
Localization lead	`
Accessibility lead	`
QA lead	`
UX lead	`
Product marketing lead	`
Operations lead	`
Additional members	`

Open issues/risks

`

Stage 1: Definition

1. Feature overview

A user should be able to keep bookmarks (and may be logins) in sync with Google Chrome.

2. Users & use cases

Users use more than one browser engine at the same time (because there is no one solution that fits all). Lets say they are developers or researchers on a dual display or within several virtual machines and they use one browser (chrome) for everything personalized, identity based and another browser for everything else. Or one browser is managed by corporate IT and another one is your unmanaged playground ...

Having the ability to keep bookmarks in sync would be great. Although one might use KeePass to store passwords across many vm's, browsers and domains, some might also want to keep their passwords in sync across different browser engines.

3. Dependencies

`

4. Requirements

`

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

`

Feature details

Priority	Unprioritized
Rank	999
Theme / Goal	`
Roadmap	`
Secondary roadmap	`
Feature list	`
Project	`
Engineering team	`

Team status notes

	status	notes
Products	`	`
Engineering	`	`
Security	`	`
Privacy	`	`
Localization	`	`
Accessibility	`	`
Quality assurance	`	`
User experience	`	`
Product marketing	`	`
Operations	`	`