No one wants to troubleshoot a card decline by logging into their mobile browser bank account in checkout at the grocery store.

You’re missing the point. Understanding how Unity works fundamentally makes you a better Unity dev.

I’m currently migrating the codebase to Swift 6 and dealing with the new concurrency system.

The idea is to guide spending before it happens, not just track transactions afterward.

I'm currently working on the paycheck prediction algorithm so Envelope can automatically determine how much needs to be set aside from user's paychecks so their bills are paid on time.

It's probably because the main measuring instrument (a probe thermometer) doesn't provide any feedback about fat rendering, moisture, etc. Plus, every brisket cut has different fat ratios and thickness, which means a recipe can't guarantee identical inputs like bread baking. I'd love for someone to throw some over the top engineering & experimentation at this.

- Push notifications within seconds of swiping your card - Frictionless to check your balance/budget/cards with bio auth - Mobile check deposit (as others here have stated) - Instantly locking/unlocking your cards - Budgeting built-in

If, to you, "doing online banking" means "sitting down at my computer and scrolling through the PDF statements on Chase's website" (I don't blame you, I've been there), then yes, doing that on a desktop is much easier. I'd encourage you to take a look at how far banking apps have come recently.

It's a budgeting app I'm building for iOS and Android. It's an alternative to YNAB, Goodbudget, or Monarch, but the checking account and debit cards are built-in, so it avoids the unreliable syncing issues that make budgeting apps suck. It's named after the digital envelope system and helps you organize money into categories for bills, spending, savings, upcoming expenses, etc. Individual and joint accounts.

Right now I'm working on an upcoming paycheck detection system to automatically split your paycheck across your budgets.

The enemy locomotion in Arc Raiders was almost entirely created with reinforcement learning. It’s a very impressive modern example (the game has been out for less than 6 months).

Here’s the documentary explaining how the RL locomotion works. Skip to 10 min 36 sec. https://www.youtube.com/watch?v=DRlhpzc7ImA&t=636s

Envelope budgeting (the method) works by allocating money up front so future obligations are actually covered before spending happens. But the hard part is handling income timing and paycheck variability without overfunding the future.

Anyways, I’m currently adding a cash flow detection algorithm to Envelope (the budgeting app) https://envelopebudgeting.com that only allocates paychecks to obligations before the next paycheck unless future funding is strictly required. That approach has avoided a lot of timing edge cases I kept running into.