Skip to content

[Tracking] Import phonebook contacts into New Expensify #47938

Closed

Description

@roryabraham

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.

Issue OwnerCurrent Issue Owner: @perunt

Activity

  1. self-assigned this
    on Aug 23, 2024
  2. moved this from Polish to Release 3: Autumn 2024 (Nov) in [#whatsnext] #wave-collecton Aug 23, 2024
  3. roryabraham commented on Aug 23, 2024

    @roryabraham
    ContributorAuthor

    First predesign questions:

    • How should we show these?

      • 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:
      image
    • 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.
  4. roryabraham commented on Aug 23, 2024

    @roryabraham
    ContributorAuthor

    posted first predesign (saving library/implementation details for a 2nd predesign):

    https://expensify.slack.com/archives/C01GTK53T8Q/p1724440169163019

  5. trjExpensify commented on Sep 2, 2024

    @trjExpensify
    Contributor

    Posted here, but I don't think this is a project for #wave-collect.

  6. roryabraham commented on Sep 2, 2024

    @roryabraham
    ContributorAuthor

    Moved to #f1-25june2025

  7. 206 remaining items

  8. roryabraham commented on Jul 3, 2025

    @roryabraham
    ContributorAuthor

    @perunt aren't there a number of other search components that need to hook into the native contact import still?

  9. melvin-bot commented on Jul 7, 2025

    @melvin-bot

    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!

  10. mallenexpensify commented on Jul 7, 2025

    @mallenexpensify
    Contributor

    @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.

  11. 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
  12. roryabraham commented on Jul 7, 2025

    @roryabraham
    ContributorAuthor

    @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.

  13. mallenexpensify commented on Jul 7, 2025

    @mallenexpensify
    Contributor

    Contributor+: @DylanDylann due $1500 via NewDot

  14. jayeshmangwani commented on Jul 20, 2025

    @jayeshmangwani
    Contributor

    @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?

  15. roryabraham commented on Jul 21, 2025

    @roryabraham
    ContributorAuthor

    I’m not aware of any active development of this feature, so I’d say proceed in that other issue

  16. perunt commented on Jul 24, 2025

    @perunt
    Contributor

    Yes, you can handle it. I'll be happy to jump in and help with anything remaining when I'm back from vacation

  17. roryabraham commented on Aug 14, 2025

    @roryabraham
    ContributorAuthor

    Closing this as complete

  18. quinthar commented on Aug 28, 2025

    @quinthar
    Contributor

    Approved for $1500

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions