Feature/home redesign

[rodvar]

• Implementation for Home: User interactions & data #97
• provided generic way of navigating to URL using default browser and applied to home navigations
• Same for blocking UI, with examples on avatar and this home screen. This fixes double-tap UI issues
• Start Trading takes the user to the Buy/Sell trading screen
• Applied new desing to home screen
• fix breadcrum navigation bug on leaf click

[nostrbuddha]

One issue. This happens at times, not always.

1. I click on 'Learn more' to open the URL in external browser (Chrome here).
2. Press hardware back button to get back to Bisq app.
3. 'Start trading' is now disabled.

Start.trading.-.Disabled.-.Shorter.mov

Tested and happens in both androidNode and androidClient.

[nostrbuddha]

1. 'Published Profiles' count is pending from 'domain/services'?

2. isInteractive is a great idea :-)
   Just a suggestion to improve it further. Rather than enabling/disabling UI controls, the logic can be moved to BisqScroll/StaticLayout, which observes for this state change. And when isInteractive is set to true, it render a transparent box over the whole screen, which captures all user input's, thus disabling the controls below. I can do it it next PR. Let me know.

[rodvar]

@nostrbuddha buddha thanks for taking the time of reviewing my PR and spotting that bug - well done 💪
I'll fix it in a commit in a bit.

Regarding your questions above:

1. correct
2. I think that's a great improvement, so we don't have to apply the verification on every single interactive button/link. Happy to get that in in your next PR! We just need to make sure that it only disables the UI whilst processing specific stuff (as bugs like the ones you discovered above are not nice for the UX 😆 ).

Cheers!

[rodvar]

branch rebased

[rodvar]

@nostrbuddha please have a look at my commit and review again when you have some time. You helped spotting a major issue that would certainly bring problems in the future so great we tackled it now ;) cheers!

[nostrbuddha]

2. I think that's a great improvement, so we don't have to apply the verification on every single interactive button/link. Happy to get that in in your next PR! We just need to make sure that it only disables the UI whilst processing specific stuff (as bugs like the ones you discovered above are not nice for the UX 😆 ).

• Yes. I will do this in the other pending PR, tomorrow night.