Open saubyk opened 4 years ago
Hi (I'm with the Boltz team),
3. On the navigation, RTL will have a service menu at the same level as Lightning, to house swap services. The menu can be labeled as
Service Add-ins
.
ACK
This menu should be enabled only when the user opts into activating any or every service option available.
That's where I have doubts/concerns. Where would that opt-in take place if not in the Service Add-ins
menu itself? You previously mentioned via conf file, which I personally consider bad UX also via a yet separate Service Add-ins
activation menu somewhere else (like in Settings
is similarly bad UX. First and foremost bad for "discoverability" of the available services. Why not simply list all available services in the Service Add-ins
menu and have it always there, either as Service Add-ins > Service Overview
with a toggle to activate the service (default all off) OR better directly as e.g. Service Add-ins > Boltz
/ Service Add-ins > Loop
which has the activation subpage with infographics, service description, fees etc all there. I believe most users would want to learn something about the service before activating it, that's the page they could do this and also activate the service.
4.
Loop
andBoltz
will be placed as separate menu items underService Add-ins
, allowing service specific brand placements like infographic and service nomenclature on their respective pages.
ACK, just that your sceens show Boltz & Loop together in the Channel Withdrawal/Deposit
pages. Could you clarify what kind of content you would envision to be placed in e.g. Service Add-ins > Boltz
and where to place the actual Channel Withdrawal/Deposit
menu once one or more services were activated?
Ty, we are thrilled working on this!
Hi, (I'm from Boltz team as well)
Adding on to what @armurbalda described, I have taken the liberty to mock up a quick wireframe for, what in our humble opinion, would be the most optimal UX for RTL + Boltz flow. This also builds adequate primitives for RTL's potential future roadmap. Let us know what you make of it. We are looking forward to discuss this more on our Saturday call. Below I attempt to reason through the UX decisions I took in the mockup.
This menu should be enabled only when the user opts into activating any or every service option available.
Self custodial lightning tools are riddled with user experience friction. Solving it is another vector of value alignment between us two projects. Activating menu via config requires a notch higher familiarity with command line toolings and raises the bar to entry, so to speak. Hence the concerns from @armurbalda. We propose for RTL to have a separate "Swap Add-in" tab akin to a marketplace, as depicted:
This solves two issues:
Installing
Boltz Swaps, the user would be explicitly granting the consent.
- Loop and Boltz will be placed as separate menu items under Service Add-ins, allowing service-specific brand placements like infographic and service nomenclature on their respective pages.
That's just the gist of our thinking process behind the proposal. As a final thought: Having a smooth UX is the USP of Boltz. The fact that users can get up and running with LN channels as soon as they install RTL could be truly magical. And we hope to get this shipped together asap!
I disagree with turning RTL into software manager and everything else but kitchen sink. There are plenty of software managers already, it's their job to provide the appropriate user experience.
There are at least three bitcoin projects I know of that provide higher-level user experience:
As a maintainer of one of them, I'll be happy to receive suggestions for UX improvements and PRs. I plan to create a UI similar to what you suggested for installing packages and node management. It will be separate from RTL or any other Bitcoin project in order to keep it clean. RTL is already packaged there as well as other things. (Although it broke for some weird reason, I'm going to fix it soon.)
Ultimately, installing RTL manually already requires editing configs etc, which is fine because users are not supposed to do it manually. :)
Swap Out
orLoop Out
depending on the service activated in the config. If both services are activated, the name on the dashboard can be generic and nomenclature can follow the brand, after user selects the service to execute the swap with.Lightning
, to house swap services. The menu can be labeled asService Add-ins
. This menu should be enabled only when the user opts into activating any or every service option available.Loop
andBoltz
will be placed as separate menu items underService Add-ins
, allowing service specific brand placements like infographic and service nomenclature on their respective pages.