In my mental model of an offline app, I expect instant responses. However, I know to the complexities of apps, the diverse wants of a big, diverse user base that it can be hard/impossible for an app to be well-architected enough to achieve this ideal.
Failover is hard, and there generally aren't hard rules for what to do if data isn't available or how to communicate to a user in a specific offline situation on how the current state of an offline app affects what they see -- and even when they would care or what they could do about it when they do care
Some day in the near future, the marketing department will wonder why so many people were curious about all of their products after browsing Organic Ground Beef[0]
I created a test group with 3 users and 3 expenses with different payers and payees. After the first reimbursement, the remaining 2 balances were not equal: -0.70 vs. 0.69. After the second, the final balances are:
-0.01
0.00
0.00
Some nice to haves:
- When creating expenses, a select all functionality/default all for "paid for"
- Group status on the /groups page
Failover is hard, and there generally aren't hard rules for what to do if data isn't available or how to communicate to a user in a specific offline situation on how the current state of an offline app affects what they see -- and even when they would care or what they could do about it when they do care