View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008894 | Taler | wallet (iOS App) | public | 2024-06-04 17:55 | 2024-06-05 01:51 |
Reporter | MarcS | Assigned To | MarcS | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | assigned | Resolution | open | ||
Product Version | 0.12 | ||||
Target Version | post-1.0 | ||||
Summary | 0008894: Pull-to-Refresh (if no pending transactions exist) | ||||
Description | In the 'Transactions' list view in iOS Taler Wallet, you can use pull-down-to-refresh to reload the list when you're waiting for e.g. a withdrawal to finish. But if there are no pending transactions, then pull-down-to-refresh cannot provide new data, but fools the user into thinking something COULD happen. However, if we just disable pull-down-to-refresh if no pending transactions exist, then the user will experience "it doesn't work" and cannot determine why it works sometimes - and doesn't most of the time, and will stop trying, thinking the app is buggy. Thus we need to keep pull-down-to-refresh enabled, but inform the user "Currently there are no pending transactions which might finish in the background. Refreshing will not deliver newer data". On the other hand, pull-down-to-refresh is not really useful for a financial app. It makes sense for eg. social networks where fresh data is generated every second, and the user pulls down when they are ready to receive new posts (and get rid of older ones), but in our case the UI should update automatically whenever new data arrives (triggered by wallet-core notifications). ==> We should probably remove pull-down-to-refresh completely. | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2024-06-04 17:55 | MarcS | New Issue | |
2024-06-04 17:55 | MarcS | Status | new => assigned |
2024-06-04 17:55 | MarcS | Assigned To | => MarcS |
2024-06-05 01:51 | Christian Grothoff | Target Version | 0.12 => post-1.0 |