You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add an option to auto-populate user-selected "Most visited sites" into "My shortcuts".
Description
There are currently two methods for adding web shortcuts to daily.dev; importing most visited sites from a supported browser (Chrome, Edge), or manually adding custom shortcuts to ‘My shortcuts’ via the adding custom shortcuts flow. At the moment, these options are mutually exclusive. A user can import their “Most visited sites,” but they cannot modify, add, or remove any of them. Or, the user can manually enter URLs into “My shortcuts,” but they cannot opt to automatically move any “Most visited” sites to their “My shortcuts,” they must add them all manually. My suggestion is to add an additional auto-populate most visited sites option to the adding custom shortcuts flow. This addition would streamline the process of adding custom web shortcuts without sacrificing user control or privacy.
Use Case
Adding an auto-populate most visited sites option to the adding custom shortcuts flow combines the convenience of importing a user's most visited sites with the flexibility of creating their own.
User Stories
1: Auto-Populate Most Visited Sites in Custom Shortcuts Flow
As a user who frequently visits certain websites, I want an option to auto-populate my most visited sites when adding custom shortcuts, so that I can quickly add commonly used websites without manually entering them.
Acceptance Criteria:
An "Auto-populate Most Visited Sites" button is available in the "Add Custom Shortcuts" flow.
Clicking the button pulls data from the browser's most visited sites.
The user can select/deselect sites before adding them to "My shortcuts."
2: User Control Over Auto-Populated Shortcuts
As a user who values control over my shortcuts, I want the ability to review and customize which most visited sites are added, so that I have control over which shortcuts appear in "My shortcuts."
Acceptance Criteria:
The auto-populated list is displayed before adding to "My shortcuts."
Users can remove individual sites before finalizing the list.
A confirmation action is required before saving the shortcuts
The user can add additional sites to "My shortcuts" after the selected URLs from "Most Visited Sites" are populated.
Solution Proposed
A new "Auto-populate Most Visited Sites" button should be added to the "Adding Custom Shortcuts" flow. Clicking this button will:
Check for, and request if needed, permission to import 'Most Visited' sites from browser.
Fetch most visited sites from user's browser.
Display a list of suggested sites where users can:
Select/deselect sites.
Edit shortcut names/URLs before saving.
Allow users to confirm and add selected sites to "My shortcuts."
Return the user to "My shortcuts" after confirming their selections.
Alternatives Considered
Automatically add most visited sites to "My shortcuts after opt-in" → Rejected due to lack of user control when transitioning from "Most visited sites" to "My shortcuts".
Allow editing of "Most visited sites" after import → Rejected due to potential loss of synchronization between the "Most visited sites" list and users' actual browsing behavior.
Additional Context
Related Documentation:
- Importing Shortcuts from Chrome to daily.dev: https://docs.daily.dev/docs/getting-started/browser-extension-installation#importing-shortcuts-from-chrome-to-dailydev
- Adding Custom Shortcuts to daily.dev: https://docs.daily.dev/docs/getting-started/browser-extension-installation#adding-custom-shortcuts-to-dailydev
Code of Conduct
I follow the conditions of this project.
The text was updated successfully, but these errors were encountered:
Concise Description
Add an option to auto-populate user-selected "Most visited sites" into "My shortcuts".
Description
There are currently two methods for adding web shortcuts to daily.dev; importing most visited sites from a supported browser (Chrome, Edge), or manually adding custom shortcuts to ‘My shortcuts’ via the adding custom shortcuts flow. At the moment, these options are mutually exclusive. A user can import their “Most visited sites,” but they cannot modify, add, or remove any of them. Or, the user can manually enter URLs into “My shortcuts,” but they cannot opt to automatically move any “Most visited” sites to their “My shortcuts,” they must add them all manually. My suggestion is to add an additional auto-populate most visited sites option to the adding custom shortcuts flow. This addition would streamline the process of adding custom web shortcuts without sacrificing user control or privacy.
Use Case
Adding an auto-populate most visited sites option to the adding custom shortcuts flow combines the convenience of importing a user's most visited sites with the flexibility of creating their own.
User Stories
1: Auto-Populate Most Visited Sites in Custom Shortcuts Flow
As a user who frequently visits certain websites,
I want an option to auto-populate my most visited sites when adding custom shortcuts,
so that I can quickly add commonly used websites without manually entering them.
Acceptance Criteria:
2: User Control Over Auto-Populated Shortcuts
As a user who values control over my shortcuts,
I want the ability to review and customize which most visited sites are added,
so that I have control over which shortcuts appear in "My shortcuts."
Acceptance Criteria:
Solution Proposed
A new "Auto-populate Most Visited Sites" button should be added to the "Adding Custom Shortcuts" flow. Clicking this button will:
Alternatives Considered
Automatically add most visited sites to "My shortcuts after opt-in" → Rejected due to lack of user control when transitioning from "Most visited sites" to "My shortcuts".
Allow editing of "Most visited sites" after import → Rejected due to potential loss of synchronization between the "Most visited sites" list and users' actual browsing behavior.
Additional Context
Code of Conduct
The text was updated successfully, but these errors were encountered: