Customize the name of a shortcut #5047
Comments
@apbitner I think we could use some UX feedback here. How should we differentiate between PWAs (with fixed names) vs homescreen shortctus to users? |
Here's what I have in my PWA designs, so it'd be a different dialog - https://mozilla.invisionapp.com/share/RGSCJEGJM8T#/366942530_Screens_-_PWA_-_Android_Add |
Since that screen is displayed by the system, it would also appear for shortcuts. Users would see two dialogs: entering the name, then pinning the shortcut. |
Regular site shortcuts will have the custom renaming dialog followed by the system dialog. And then PWA's will just have the system dialog. |
Okay, so it sounds like we'll just accept the confusion a user might encounter if they can't tell what situations they see a rename dialog, vs not. |
If we want to turn off the feature, it'd be an E2. UX wants the feature to ship complete, so the two options are:
|
- Changes MainScope to viewLifecycleScope - Fixes string name/comment to better describe what it is - Adds disabled state to the add button
- Changes MainScope to viewLifecycleScope - Fixes string name/comment to better describe what it is - Adds disabled state to the add button
- Changes MainScope to viewLifecycleScope - Fixes string name/comment to better describe what it is - Adds disabled state to the add button
Verified that the user can customize the name of a shortcut when using "Add to Home screen". @boek |
@softvision-miralobontiu Good catch! I can fix here :) |
Why/User Benefit/User Problem
Shortcuts and PWAs are similar but have some distinctions.
What/Requirements
-I can choose what the shortcut will be called (InVision)
Acceptance Criteria (how do I know when I’m done?)
Shortcuts can have custom names
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: