Closed grgia closed 7 months ago
I have updated the HL Design Doc
Some questions to keep in mind for a predesign:
For Share-to-Expensify: What activity will be triggered when clicking share? Do we want users to send a message? What will our Share Sheet look like? What information can the user customize when sharing into the app? How will a user select the destination of what they are sharing? How can we design this so we can later include sharing a photo -> Scan Receipt?
For Share-from-Expensify: What content should be shareable? Should it just be photos/attachments/QR codes? Should users be able to share IOU's/Report links? How might a share be initiated? Should we use the long-press and add it to the context menu? Should a user be able to share a link to a room with a share icon/button in the chat header?
Some related libraries:
React Native
External (I suggest we consider these, as we will want the ability to better customize the share modal)
Sharing Link / Photo -> Clicking Expensify
Sharing Link / Photo -> Clicking Expensify DM
@lindboe Could you comment on this so I can assign you?
Commenting!
📣 @lindboe! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork. Please follow these steps:
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
Super excited!
:wave: Hello Generalist Track Team - you have been assigned to review this High Level Design Doc. Please, treat this as a priority. Review 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 pannel or follow these instructions.
@arielgreen
(Expensifier / Graduate) - https://github.com/Expensify/App/issues/17334@caitlinwhite1
(Expensifier / Graduate) - https://github.com/Expensify/App/issues/17335@zsgreenwald
(Project Manager) - https://github.com/Expensify/App/issues/17336@stitesExpensify
(Project Manager) - https://github.com/Expensify/App/issues/17337@conorpendergrast
(Product Manager) - https://github.com/Expensify/App/issues/17338@stephanieelliott
(Product Manager) - https://github.com/Expensify/App/issues/17339@quinthar
(Generalist) - https://github.com/Expensify/App/issues/17340@anmurali
(Generalist) - https://github.com/Expensify/App/issues/17341@HaleyJacobson
(Accounting Technical Team) - https://github.com/Expensify/App/issues/17342I have read and reviewed this Design Doc!
@arielgreen @caitlinwhite1 @zsgreenwald @conorpendergrast @stephanieelliott @quinthar @anmurali @HaleyJacobson bump on this HL doc review - https://docs.google.com/document/d/1m4BZ-fhNMnTQhWiglqMk9U2VXYDSrirjeYRLPHf3SkA/edit#
It's short and sweet, so if you have a minute to look, please do!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
Not overdue, waiting on detailed section from @lindboe
in progress
Detailed Doc Ready For Review!
:wave: Hello Generalist Track Team - you have been assigned to review this Detailed Design Doc. Please, treat this as a priority. Review 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 pannel or follow these instructions.
@arielgreen
(Expensifier / Graduate) - https://github.com/Expensify/App/issues/26453@chiragsalian
(Expensifier / Graduate) - https://github.com/Expensify/App/issues/26454@zsgreenwald
(Project Manager) - https://github.com/Expensify/App/issues/26455@stitesExpensify
(Project Manager) - https://github.com/Expensify/App/issues/26456@robertjchen
(Product Manager / Generalist + Engineer) - https://github.com/Expensify/App/issues/26457@pecanoro
(Product Manager / Generalist + Engineer) - https://github.com/Expensify/App/issues/26458@puneetlath
(Product Manager / Generalist + Engineer) - https://github.com/Expensify/App/issues/26459@yuwenmemon
(Product Manager / Generalist + Engineer) - https://github.com/Expensify/App/issues/26460@conorpendergrast
(Product Manager / Generalist + Non-Engineer) - https://github.com/Expensify/App/issues/26461@stephanieelliott
(Product Manager / Generalist + Non-Engineer) - https://github.com/Expensify/App/issues/26462@anmurali
(Product Manager / Generalist + Non-Engineer) - https://github.com/Expensify/App/issues/26463@quinthar
(Product Manager / Generalist + Non-Engineer) - https://github.com/Expensify/App/issues/26464I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
Detailed Doc Is In Review
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I'm a broken record here, but I really, really hope we ditch the iOS share extension and just open the app. It feels like 90% of the work is iOS specific, totally avoidable, and goes explicitly against our cross-platform philosophy.
(But otherwise, it looks great and I can't wait to have it!!)
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
Detailed is done, implementation was paused for wave projects. We are working on including scan pending this convo: https://expensify.slack.com/archives/C04KQL2HSQ1/p1696347905090599
I have read and reviewed this Design Doc!
Design Doc is being updated
The design doc reviewers have already been assigned to this issue. If you think this is wrong, reach out to #engineering for help.
@arielgreen @chiragsalian @zsgreenwald @stitesExpensify @robertjchen @pecanoro @puneetlath @yuwenmemon @conorpendergrast @stephanieelliott @anmurali @quinthar
We've updated the detailed doc to include smart scanning in V1. I re-added the label and it did not reassign you as reviewers, so if you're interested in taking a look at the update from the last review, please check out the following updated DD and leave a review!
https://docs.google.com/document/d/10agvPMrVzXViEaH47gAXr9CZN62aaI3L5kj4aoj5LhI/edit
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
I have read and reviewed this Design Doc!
Design Doc
https://docs.google.com/document/d/10agvPMrVzXViEaH47gAXr9CZN62aaI3L5kj4aoj5LhI/edit
Proposal
Let’s implement native share menus so users can both share-to and share-from New Dot.
Problem: There are plenty of times where I want to share something from outside our app into New Expensify. But there’s no way to quickly share links/photos/information while outside Expensify. For example, if I’m in the Photos App and I decide I want to share a photo, I’ll have to leave the app → open New Dot → go to the correct chat → click add attachments → find the same image again → and so on. On the flipside, there’s no easy way to export information from inside the app to outside Expensify. There’s no quick solution to export a PDF to print or to AirDrop a photo from one device to another.
Solution: Let’s utilize one of our external agencies to implement Native Share Menus. Share menus are an essential feature to most other chat apps. If a user wants to send a photo, let’s make it as easy as possible. From the photo app you’d just click share → New Expensify and voila! In fact, we already have this feature for Old Dot. Right now, you can take a picture -> share -> Expensify, and immediately start a smartScan. So adding Share Menus to New Dot would be a requirement to maintain feature parity between Old and New Apps. As for sharing from inside Expensify to outside sources, to make New Expensify our go-to chat and finance collaboration app in the future, we should be able to communicate with those who have not yet adopted the app. For those of us that are eager to use NewDot as our primary chat app in our day-to-day lives, this feature would be a valuable way to encourage that while the rest of the world is still using WhatsApp. Later on, external sharing can feed into our viral business model, where chats/photos/links sent from New Expensify can be wrapped in an advertising moment, incentivizing people to join New Expensify from other chat apps.
https://expensify.slack.com/archives/CC7NECV4L/p1675375866420119
Pre-designs
Initial Pre-design Design Pre-design
Tasks
#whatsnext
strategy@expensify.com
and paste in the Proposalstrategy@expensify.com
(continue the same email chain as before) with the link to your Design Docstategy@expensify.com
again with links to the doc and pre-design conversation in SlackDesignDocReview
label to get the High-level of proposed solution section reviewedDesignDocReview
label to this issuestrategy@expensify.com
one last time to let them know the Design Doc is moving into the implementation phasestrategy@expensify.com
once everything has been implemented and do a Project Wrap-Up retrospective that provides:Related Issues
Mockup: https://github.com/Expensify/App/issues/16256