I’m working on a small Ionic app (Angular + Capacitor) that pulls account and card balance data from an external source and displays it to the user in a simple dashboard. The technical part is fine, but I keep running into a practical problem that I’m not sure how others handle cleanly.
In the real world, balance data isn’t always instant or reliable. For example, I personally use a salary card in the UAE (FAB prepaid), and there are times when the balance hasn’t updated yet, or it’s not possible to confirm it remotely without visiting a branch. That kind of uncertainty is exactly what users complain about when they open an app and don’t trust what they’re seeing.
From an Ionic UX and state-handling perspective, what’s the best way to represent this kind of situation without misleading users? Things like:
-
balance fetched but possibly not settled yet
-
balance temporarily unavailable
-
last confirmed amount vs current estimate
I’m posting here because this forum usually has people who understand practical, real-world tech problems, not just theory, and I’m interested in how others model and communicate this kind of ambiguity inside Ionic apps without overcomplicating the UI.
Would appreciate hearing how you’ve handled similar cases in production apps, especially financial or utility-style apps.