View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011410 | Taler | wallet (all platforms) | public | 2026-05-15 22:32 | 2026-05-15 22:32 |
| Reporter | sebasjm | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0011410: first purchase on blog experience | ||||
| Description | consider the following scenario, very simple from the first demo experience 1) to to demo.taler.net using your desktop, from the you see you can install the wallet (android or ios, same) 2) install the mobile version & withdraw demo money from the stating button / onboarding 3) go to the shop __ in your desktop __ 4) pay the article with your mobile wallet now you can read the article in your desktop and the wallet shows you the fulfillment url, all fine BUT After clicking on the fulfillment URL on the recipe you experience the following 1) the wallet shows "you need to pay" for a second time (bad UX since you come from the wallet, the same you used to pay) 2) click the pay link, you go back to the wallet, completes without interaction (good!) BUT you are not redirected to the blog (bad UX, I'm coming from the blog then repurchase was triggered so the wallet should be fast and redirect back) 3) void 4) you still see the the article on desktop for on refresh it ask to pay, weird (bad UX it should poll and change automatically) Nothing is broken but I think we have a big gap for improvement: for (1) clicking the fulfillment URL from the wallet should always "steal" the session. Maybe the wallet can include the sessionID of the last purchase or something similar? for (2) I think is an UI problem (maybe present in all wallets): when the wallet is triggered by a taler:// from external source then the UI should redirect automatically to the fulfillmentURL when done. Not when it was QR or triggering behavior. I think that the repurchase detection could be faster. for (3) well, the blog should poll the backend. This is more are details but seeing fast and responsive it work is very nice first experience. Maybe also tell the user that the session lost access to the order if this is intended. I'm not entirely sure that the mutual exclusive access is needed in the example, but if it is it can be better. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-05-15 22:32 | sebasjm | New Issue |
