Create offer: user can resume last unfinished offer creation

[rodvar]

This feature involves the following:

• When user taps on create offer (from offers or from a market view), if there is an unfinished offer saved a dialog should ask "Would you like to resume your latest offer?" options: "Resume" or "Discard" (resume loads the offer progress to the latest unfinished step, discard toss the saved offer and starts the create offer flow fresh
• market prices adjustments should be done automatically on the saved offer whenever appropriate -> just apply user selections should suffice ( verify on impl )

[rodvar]

@jigglypuff-bsq @HenrikJannsen sketched this in the backlog, feel free to comment

[HenrikJannsen]

I think that adds quite some effort and complexity (like the mentioned price and amount adjustments). I think easier with a similar effect for the user is to locally persist the users selection like payment methods, etc.

[wodoro]

I think persisting the user selected options/amounts is a better UX than asking user to resume their latest offer with a dialog. I imagine it would get annoying very fast for users who are very busy, going out of the flow to answer a chat and go back to resume creating the offer etc.

and as a plus it's also much easier to implement

[HenrikJannsen]

The amount we do not persist in Bisq 2 because that causes too much troubles with price changes affecting min/max amounts and reputation based amounts. But all others including price are persisted per market (specially important for payment methods)

[jigglypuff-bsq]

Do we know if this is a demanded feature by a meaningful population? Asking because I've never thought of coming back to an exited offer and wondering if any of you have before. They also don't take much time to recreate but again, this is just my opinion. Will gladly design a UI flow for this if we think it's worth our efforts.

[wodoro]

at the very least, I want the app to remember my last used payment methods in the offer creation process
I am creating many offers for testing purposes locally every time I'm working on the app and having to select them every time is already a friction for myself

this is my opinion as a dev though, I imagine normal users may have different preferences

[rodvar]

all very good points, I'll convert this to a discussion and let's decide what to do later on and create the proper issue. I envision 2 issues from this conv.

From a user perspective @wodoro , having the app remembering your last selections is very useful for a ~7 steps process.
To avoid what you are saying we can use an expiry timestamp on the saved last offer 👍 which actually makes sense

Regarding the "preferred methods" that's a great idea and I think it should be a different feature we can create a card for it 👍