Send from a card, Arkade change check, home balances and invite links
TLDR
4 PRs merged, 2 PRs opened, 1 commit, 2 repos (the Nuri app: 5, the Arkade server: 2), 2 deployments, +166 / -7 lines of code. I worked on 2 features.
Send from a card now only preselects the From balance and Bitcoin starts on Lightning. Arkade sends that would leave too little change are now stopped before you approve them, and invite links that record who invited whom are open but not merged.
Send from a card
In the Nuri app, Send and then “Swap to my balances” used to lock the From side to the card you came from. Now it only preselects that card’s balance (Bitcoin: Lightning, Cash: the main currency) and you can pick any source. Same for Visa & Banking, Send, “To my balances”. Add money still fixes the card as the destination.
Send on the Bitcoin card used to open on Onchain as soon as Onchain had any sats. Now it opens on Lightning whenever Lightning holds money, and only falls back to Onchain when Lightning is empty. Cash still starts on the main currency. I checked on a web build with a fresh wallet that the From row lists all four balances and switching works. The pass on iOS and the installed web app is still open. It’s app only and ships as an over-the-air update, no new build.
Arkade sends with too little change
On Arkade every output of a send has to be above a minimum amount, and inputs and outputs have to add up exactly. The app only checked the amount you send against that minimum, not the change that comes back to you. So when the change landed between zero and the minimum, the server refused the send after you had already approved it with your passkey, and you got a raw error plus a pending row. A live report was exactly that, a Lightning payout where the change would have been 169 sats.
Now the app plans the send against your own coins before it asks for approval. If one more coin makes the change big enough, it uses that coin. If nothing works, it stops with “max amount entered” and the real maximum, so nothing is signed, there is no passkey prompt and no pending row. The send sheet also shows your balance minus that minimum as what can go out, and checks the typed amount the same way. Lightning payments funded from Arkade get the same check.
Home name and balances
After signing out and back in, the home greeted people without their name and showed 0,00 on euro, dollar, card and IBAN while the balances were still loading. Nothing was lost, the screen just showed zero for a balance it had not read yet. Now an unread balance shows the unknown mark and a balance that is really empty still shows 0,00. The greeting stays empty until the name is known and keeps its height, so the header does not jump. The card adds nothing to the total until its first read lands. Tests pass, the device pass on iPhone SE and Android Chrome is not done yet.
Pay page cleanup
I removed two things from the pay page in the Nuri web app. The Open in Nuri button is gone, it sat over the keypad’s bottom row on a phone and confused payers who don’t have Nuri. A payment link now offers the automatic handoff to the app or an external wallet, nothing else. The empty top bar is gone too, it pushed the From card 72px down on the first screen. The back arrow still shows once there is a payment target, and the automatic handoff works as before. Android Chrome does not open the app from the page without a tap, and I decided not to add any button for that.
Invite links
This is not merged yet, I opened one PR in the app and one on the server. Opening an invite link on app.nuri.com/invite/ followed by a username keeps the inviter on the device, shows the normal welcome and signup, and the address bar goes back to app.nuri.com. The inviter is sent along with the username claim, so there is no extra passkey prompt, and it is forgotten once the claim succeeds. The first invite opened on a device wins. The existing app.nuri.com/@username link stays the login link.
The server stores who invited whom only when the claim creates a new user, once, and never changes it. An unknown or inactive inviter, or your own name, is ignored and signup goes through as before. Tests are green on both sides. The app needs the server change deployed first, until then the server ignores the inviter.