mutinywallet / mutiny-web-poc Goto Github PK

instead of coming up with our own terms for everything we could just handle bip21 query params directly...

only lame part is that bip21 amounts are in "bitcoin" so we'd always have to convert to sats

404 page is not enough!

Happened to me while working on a plane. Thought it was the bitcoin price api but I stubbed that out and the issue still existed. Maybe we are getting a font from the internet?

I use the Dark Reader firefox extension to force darkmode on websites. It seems to break the QR code:

Can import pre built wasm blob

Also could do a local sqlite for persistence

not sure why I have to manually refresh the balance after going home. I even invalidate the balance query when you click the "nice" button on the receive final screen

Should be able to view logs and also download a text file of your current session's logs

Any time a sync is happening, which by default seems to be all the time, any logs get put into a collapsed BDK Sync label and I can't see what I'm trying to find.

Further these BDK Sync logs should probably be quieted.

Display a QR code for the mutiny connection string, and allow others to scan the QR code to connect peer.

like it included the invoice description (and maybe the payment hash too?)

to repro: send to a lightning invoice

then send again to just a basic bitcoin address

should get rid of a lot of redundant toaster components, just need to find a good spot to put it

solve chicken egg problem! probably warn about clearing too

probably a lot of other failures we don't explain to the user as well but this is a good start

like muun basically

when i send 10M sats to my node, get those confirmed, then open 100k sat channel and sync, my balance is 10,100,000 balance. eventually it corrects itself.

maybe a warning, maybe init first node when you init node manager for the first time, maybe load on chain by default, few options

Note1: I can make these separate tickets if that's easier!
Note2: If there's a Figma for this I can make specific change suggestions. If not we could start one!

Goals

• Identify quick wins

Non-goals

• Rethink brand identity (colors, type, etc)

A few super quick wins

• Trigger numeric keyboard any time a number field is focused on (see figma)
• Copy button is going outside of the margin (see figma)
• Move menu button trigger to top right, so position is consistent
• Make all buttons full width on mobile (instead of staggered and left aligned)
• Center sats amount on homepage - this is the hero number!

Bigger changes

• Font readability on some pages (eg. Transaction page, font weight on buttons)
• Warning banners for state/seed backups
• Confusing guidance around saving seed vs state (see figma/video)

Figma notes
https://www.figma.com/file/TAhivKvpgOl6C4oInznnuS/Mutiny-feedback?node-id=0%3A1&t=a2ZqrUF7wq8W6LbV-11

Video walkthrough
https://photos.app.goo.gl/2D3WVKpxujtorZcT8

Followup to MutinyWallet/mutiny-node#246

1. pay an invoice
2. click X instead of "nice"
3. now that you're at the home scree, click receive
4. it will show you a receive screen instead of allowing you to create a new invoice or on chain address

I don't know how to refresh my "version" without uninstalling and reinstalling the pwa

Similar to this MutinyWallet/mutiny-node#309

When I am in the browser and go through the send phase, it doesn't stop the camera and it persists until restart.

I'm creating an issue for this because I'm already down the rabbit hole and it's not going well. Typescript + jest + create react app + craco... a lot of shenanigans for something that should be straightforward.

Tried following this guide but it isn't working for me: https://dev.to/brandonwie/absolute-paths-in-cra-setting-using-craco-feat-typescript-and-ts-jest-2301

Basically, I use typescript path aliases like @compoenent to make imports cleaner. But jest / ts-jest needs to be informed of this because apparently it does its own module resolution.

I'm tempted to cut my losses and migrate the whole thing over to vite / vitest / vite pwa