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
{{ message }}
Repository navigation
[Tracking] Import phonebook contacts into New Expensify #47938
Proposal: Import phonebook contacts into New Expensify
Strategy
The most important metric we want to see grow in the coming months is new user acquisition 📈. To facilitate that we need to invest in features that streamline viral user growth and make it easier to pull new users into the app. 👥
Problem
If you want to use the Expensify Classic app to invite your team or your boss to Expensify, it’s very easy. You sign up, scan a receipt, and an inbox task will appear asking who you want to send it to. If you click on that, it will open your phone’s contact book and allow you to select the contact(s) that you want to invite to Expensify. You can invite people you know in just a few taps, without leaving the app.
There are a number of other places throughout Expensify Classic where you can easily invite people to Expensify, such as when submitting reports.
Meanwhile, in New Expensify, the first few steps of inviting new users are arguably more streamlined. You immediately scan a receipt, and on the very next page you’ll be asked who you want to share it with. However, at that stage, you need to leave the app to find their email or phone number from some other source and manually type or copy/paste it into NewDot. This introduces friction in a critical viral growth moment.
Solution
Let’s close the gap on one of the final pieces of feature parity between Expensify Classic (mobile) and NewDot, by importing contacts from your phonebook 📕 into New Expensify. This will streamline the process of inviting people you already know into Expensify. Let’s show these imported contacts in any page where we invite new users (start chat, workspace invite, request money participants page, etc…).
All these pages are already set up to invite new users to Expensify via their email or phone number, so the only requirement is to import that information from the contacts app (after obtaining the user’s permission to do so). Because of that, this project is completely front-end and self-contained. That means that after we get through an initial high-level design phase, it can be implemented entirely by external contributors.
For UI inspiration, WhatsApp 📞 shows imported contacts in an “Invite to WhatsApp” section.
I suggest we just show a new section in selection lists titled Invite to Expensify, styled the same as the existing Recents and Contacts sections:
Should we try to support web?
I suggest no (for the V1, anyways). There's an experimental ContactsManager web API, but it only works on Android atm. Furthermore, it doesn't support importing all contacts and displaying them using our own UI. Instead, it's more like what we have in OldApp that pulls up the native contacts app and allows you to select contacts to import.
Should we try to support desktop?
I suggest yes. It may be a bit involved to set up, but fortunately our needs should be pretty simple. It might look something like this:
Use the same Swift code to access contacts on macOS and iOS. CNContactsStore works on both.
Use the same C+code on iOS and macOS to create C++ bindings for the swift code
(here's where things start to differ) on desktop, create a Node.js addon with JS bindings to the C++/Swift code
Require the Node.js addon in desktop/main.ts
Use the Electron context bridge to provide a renderer process interface for the Node.js code that can be used to access contacts
Should we use a library for this?
There are a couple of options, such as react-native-contacts and expo-contacts. However, because the native code should be quite simple and none of the existing solutions support (or would be expected to support) Electron, I suggest we just create our own small library for this.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
@roryabraham , saw "Due for payment 2025-06-18" and that Zany was assigned as BZ. She's OOO, please tag me if a payment is due this week. I'm removing the payment pretext in the title too.
changed the title [-][Due for payment 2025-06-18] [Tracking] Import phonebook contacts into New Expensify[/-][+][Tracking] Import phonebook contacts into New Expensify[/+]on Jul 7, 2025
@mallenexpensify I do think payment should be issued to @DylanDylann for their role as C+ for #54459. Furthermore, I discussed with @blimpich and we agreed that $1500 feels like a more appropriate bounty amount for this issue than the standard $250.
@perunt@roryabraham , We have an open issue #65916 where imported contacts aren't showing on the Start Chat page. Just wanted to confirm - do we have any ongoing PR for this, or can we go ahead and work on fixing it independently of this issue?
Activity
roryabraham commentedon Aug 23, 2024
First predesign questions:
How should we show these?
Invite to Expensify, styled the same as the existingRecentsandContactssections:Should we try to support web?
Should we try to support desktop?
CNContactsStoreworks on both.desktop/main.tsShould we use a library for this?
roryabraham commentedon Aug 23, 2024
posted first predesign (saving library/implementation details for a 2nd predesign):
https://expensify.slack.com/archives/C01GTK53T8Q/p1724440169163019
trjExpensify commentedon Sep 2, 2024
Posted here, but I don't think this is a project for #wave-collect.
roryabraham commentedon Sep 2, 2024
Moved to #f1-25june2025
roryabraham commentedon Sep 3, 2024
Predesigns two and three:
206 remaining items
roryabraham commentedon Jul 3, 2025
@perunt aren't there a number of other search components that need to hook into the native contact import still?
melvin-bot commentedon Jul 7, 2025
This issue has not been updated in over 15 days. @shawnborton, @blimpich, @roryabraham, @perunt, @zanyrenney, @DylanDylann eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
mallenexpensify commentedon Jul 7, 2025
@roryabraham , saw "Due for payment 2025-06-18" and that Zany was assigned as BZ. She's OOO, please tag me if a payment is due this week. I'm removing the payment pretext in the title too.
[-][Due for payment 2025-06-18] [Tracking] Import phonebook contacts into New Expensify[/-][+][Tracking] Import phonebook contacts into New Expensify[/+]roryabraham commentedon Jul 7, 2025
@mallenexpensify I do think payment should be issued to @DylanDylann for their role as C+ for #54459. Furthermore, I discussed with @blimpich and we agreed that $1500 feels like a more appropriate bounty amount for this issue than the standard $250.
mallenexpensify commentedon Jul 7, 2025
Contributor+: @DylanDylann due $1500 via NewDot
jayeshmangwani commentedon Jul 20, 2025
@perunt @roryabraham , We have an open issue #65916 where imported contacts aren't showing on the Start Chat page. Just wanted to confirm - do we have any ongoing PR for this, or can we go ahead and work on fixing it independently of this issue?
roryabraham commentedon Jul 21, 2025
I’m not aware of any active development of this feature, so I’d say proceed in that other issue
perunt commentedon Jul 24, 2025
Yes, you can handle it. I'll be happy to jump in and help with anything remaining when I'm back from vacation
roryabraham commentedon Aug 14, 2025
Closing this as complete
quinthar commentedon Aug 28, 2025
Approved for $1500