UX Overhead
(UXPROD-836)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | UX Overhead |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Khalilah Gambrell | Assignee: | Khalilah Gambrell |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | technical, ux | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue links: |
|
||||||||
| Epic Link: | UX Overhead | ||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||
| Rank: Duke (Full Sum 2021): | R4 | ||||||||
| Rank: FLO (MVP Sum 2020): | R4 | ||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||
| Rank: hbz (TBD): | R4 | ||||||||
| Rank: Hungary (MVP End 2020): | R4 | ||||||||
| Rank: Leipzig (Full TBD): | R4 | ||||||||
| Rank: Leipzig (ERM Aut 2019): | R4 | ||||||||
| Description |
| Comments |
| Comment by Filip Jakobsen [ 10/Jul/18 ] |
|
The idea with this component is to A) provide a consistent experience for end users across apps, B) make it easy for app developers to create edit screens that are functional, accessible and interoperable with the rest of the system, and C) make it possible for third party developers to write apps that can integrate with these forms. I did a quick sketch of some of the requirements for this component, and which elements / functions could or should be able to be registered by the app in question, or with the app in question, by other apps, through the platform itself. This is how I envision we can do it best. Let me know if you have any questions, advice or ideas about all of this. Thanks! |
| Comment by Khalilah Gambrell [ 03/Sep/18 ] |
|
Filip Jakobsen, Rasmus Wølk, and John Coburn, I am placing this user story into Draft until the description is more understood. Early implementers will never prioritize work on this feature without a more defined description. And it can never be assigned to other developers to begin the work without more details. |
| Comment by Rasmus Wølk [ 05/Sep/18 ] |
|
I'd like to discuss the implementation of this issue further with John Coburn. I'll reach out to him on Slack. |
| Comment by Khalilah Gambrell [ 05/Sep/18 ] |
|
Hey Filip Jakobsen and Rasmus Wølk, it is not clear what we are trying to solve with this feature. Can you provide more description of this feature? I am also unsure what makes this a high priority feature. |
| Comment by Filip Jakobsen [ 05/Sep/18 ] |
|
This task fits in the UX overhead category. As such we should not attempt to have implementers or users prioritize it, because in itself it provides no solutions or features to users. It is a piece of a larger infrastructure meant to support a consistent, predictable layout and behavior of the system across apps; and to support the adding of cross-app plugins, features or shortcuts for e.g. navigation, semi-automatic form filling and general usability. I am happy to explain further in a call if needed. |
| Comment by Khalilah Gambrell [ 07/Sep/18 ] |
|
Blocking until team can break this Feature into user stories that can be added to the backlog. |
| Comment by Khalilah Gambrell [ 07/Sep/18 ] |
|
Rasmus Wølk - John and Jeffrey recommend the following to get this feature unblocked
|
| Comment by Rasmus Wølk [ 12/Sep/18 ] |
|
Khalilah Gambrell Sounds like a plan. Thanks - I'll look into this next week. |
| Comment by Cate Boerema (Inactive) [ 13/Sep/18 ] |
|
UXPROD feature assignee = product owner. I am assigning this to Khalilah for now, as she is the temporary PO for UX/stripes |