Feature request: authorize third-party API apps from inside the Splitwise mobile app (app/universal-link OAuth) #96

Hi Splitwise team,

We're building an AI money manager that runs on WhatsApp. Users ask it to follow up with friends who owe them money, and it reads their Splitwise balances through the API (OAuth, read-only, user-authorized).

The problem
The only authorization path we can find is the browser flow. The user taps a link in WhatsApp, lands in WhatsApp's in-app browser, and has to log in to Splitwise on the web and approve the consent screen. Most of our users already have the Splitwise app installed and logged in, but the browser flow doesn't use it. In our early traffic, most users who receive the connect link abandon at the web login step.

What we're asking

1. Does Splitwise support authorizing a third-party API app from inside the Splitwise mobile app? For example, an Android App Link or iOS Universal Link on the authorize URL that opens the app, shows the consent screen for the logged-in account, and returns to the app's https redirect URI. If it exists, could the docs cover it?
2. If it doesn't, would you consider adding it? Approving with one tap in the already-logged-in app, instead of a fresh web login, would make it much easier for partners to build on Splitwise.
3. In the meantime, is there a recommended way to reduce login friction in the browser flow, such as session reuse or "Continue with Google / Apple", for users arriving from an in-app browser?

Details

• App type: server-side OAuth 2.0 authorization-code app, read-only use (balances, friends, expenses).
• Flow: WhatsApp message with link, then Splitwise authorize URL, then redirect to our https callback.
• Happy to beta-test or answer questions.

Thanks!