App [Wave5] NewDot: Quick Action Button

Proposal

WN Strategy: We’re migrating customers to our new superapp where an abundance of choice and feature discovery is at the forefront to encourage them to “land and expand” across a growing number of use cases. That said, it’s crucial that we maintain the streamlined usability our existing customers know and love. Getting the balance right is important for both the success of reunification, and the long term usability of our superapp.

Problem: We’ve over indexed Global Create to optimise for feature discovery, at the expense of our core use cases. Put plainly, it takes more steps to scan a receipt in NewDot than it does on the OldApp. This is important to address now as migration plans are in progress, to avoid the “first look” of our new app being one that adds more time and effort to perform an action taken a thousand times before, increasing the likelihood to return to Classic. Needless to say, this is already coming up with our employees as early adopters.

Solution: Add a quick action button to the bottom of global create. The button will record the last action you took (i.e Request Money > Scan) and the destination for it (i.e To: Duraflame, Inc.). When used for submitting receipts to a workspace like this example, we’ll also stop showing the confirmation page to enter additional expense details unless the workspace has required categories or tags for coding, a la “fire and forget” in OldApp.

Tasks

[x] Post Proposal (full Problem/Solution statement) in #whatsnext
[x] Wait at least one full business day, and until the post has a majority (2/3) of positive reactions (👍)
[x] Paste Proposal in the space above with a link to the Slack thread
[x] Email [email protected] and paste in the Proposal
[x] Fill out the High-level overview of the problem, Timeline, and Terminology sections of the Design Doc
[x] Email [email protected] (continue the same email chain as before) with the link to your Design Doc
[x] Host a pre-design meeting (example) in #expensify-open-source to discuss any necessary details in public before filling out the High-level of proposed solution section.
[x] Fill out the High-level of proposed solution section
[x] Email [email protected] again with links to the doc and pre-design conversation in Slack
[ ] Add the DesignDocReview label to get the High-level of proposed solution section reviewed
[ ] Respond to any questions or concerns and bring up blockers in Slack to get a consensus if necessary
[ ] Confirm that the doc has the minimum necessary number of reviews before proceeding
[ ] Host another pre-design meeting in #expensify-open-source to ask for engineering feedback on the technical solution.
[ ] Fill out the Detailed implementation of the solution and related sections.
[ ] Re-add the DesignDocReview label to this issue
[ ] Respond to any questions or concerns and bring up blockers in Slack to get consensus if necessary
[ ] Confirm that the doc has the minimum necessary number of reviews before proceeding
[ ] Email [email protected] one last time to let them know the Design Doc is moving into the implementation phase
[ ] Implement the changes
[ ] Add regression tests so that QA can test your feature with every deploy (instructions)
[ ] Send out a follow up email to [email protected] once everything has been implemented and do a Project Wrap-Up retrospective that provides:
- Summary of what we accomplished with this project
- What went well?
- What could we have done better?
- What did we learn?

Jan 19 '24 14:01 trjExpensify

Current assignee @trjExpensify is eligible for the NewFeature assigner, not assigning anyone new.

Jan 19 '24 14:01 melvin-bot[bot]

Pre-design here. Threads are dying down, plan to get the HL doc together by the start of next week.

Jan 29 '24 20:01 trjExpensify

plan to get the HL doc together by the start of next week.

Alrighty, ideal nav ended up being ready to launch last week, so it knocked my timeline out by a couple of days. But the HL is now out for review.

Feb 07 '24 23:02 trjExpensify

:wave: Hello Generalist Track Team - you have been assigned to review this High Level Design Doc. Check out this Stack Overflow for some tips on reviewing a design doc. Once you are done, simply press the Add "Reviewed Doc" comment button in the right hand side K2 panel or follow these instructions.

@slafortune (Expensifier / Graduate) - https://github.com/Expensify/App/issues/36088
@johncschuster (Expensifier / Graduate) - https://github.com/Expensify/App/issues/36089
@zsgreenwald (Project Manager) - https://github.com/Expensify/App/issues/36090
@maddylewis (Project Manager) - https://github.com/Expensify/App/issues/36091
@conorpendergrast (Product Manager) - https://github.com/Expensify/App/issues/36092
@isabelastisser (Product Manager) - https://github.com/Expensify/App/issues/36093
@ryanschaffer (Generalist) - https://github.com/Expensify/App/issues/36094
@cead22 (Generalist) - https://github.com/Expensify/App/issues/36095
@heyjennahay (Accounting Technical Team) - https://github.com/Expensify/App/issues/36096
@ryanschaffer (Marketing Team) - https://github.com/Expensify/App/issues/36097

Feb 07 '24 23:02 melvin-bot[bot]