Open the app, wait a few seconds. An account data stream error will be shown to the user. Probably due to the event stream polyfill and its fetch fallback.

• Trustline management
  • Show trustlines
  • Add a trustline (manually + hardcoded list of popular ones?)
  • Remove a trustline
• Show non-XLM balances
• Allow choosing asset on payment creation

Hide the key data (encrypted?) in a JPEG image 😎

• Textual secret key export
• Textual import is already implemented
• QR import
• QR export

Have a look at https://github.com/andywer/key-store. Needs some refurbishing, though:

• use random initialization vector (!!) and store it along the encrypted password
• use tweetnacl.js
• should review the API
  • might be better to decouple the encryption and the filesystem storage logic more

Still using material-ui v0. Since v1 is stable now, it's time to migrate.

The tx submission progress box is centered inside the create payment overlay, but should be centered in the middle of the screen instead.

Wasn't really on the roadmap, but for a Friday evening experiment this is fine.

Branch: feature/33-change-wallet-page-style

By special request: Make the window pretty 😎

There is no official name for the app yet, but adding some SatoshiPay branding won't hurt.

• Add SatoshiPay icon to electron app
• Change electron app name / window title
• (Maybe) Add icon to page / header

It's quite hard to write types for. recompose in JS is great, but kind-of a hazzle in TS.

This project has been started outside of SatoshiPay. Finish the migration of the repository to its new home and make sure the code base matches the overall standards we use at SatoshiPay.

Explore the potential overlap between this wallet and a potential publisher app.

Which features can be re-used? How can they be made re-usable?

This was the last project I wrote without TypeScript. Time to change that as long as the code is not yet too large.

Preparation necessary: Ping Daniel!

New brand color: #02b8f5

Ran dev electron app using npm run dev in electron/. Created a payment in the mocked testnet wallet. Payment worked, but transaction didn't show up.

Check: Maybe the tx only gets added to the bottom of the txs list instead of at the top?

Display a useful error to the user if there is one. Use snackbar or similar.

Should be a generic solution that can be used by any part of the code.

Bad wording. Having multiple "wallets" is confusing.

There is only one wallet: Our app that the user uses. It contains a set of accounts.

Add --target=electron to the parcel invocation. Will bundle app files, but not dependencies. Should allow using node dependencies in the app code.

Make sure that node dependencies can be used. Will probably be unable to develop in the browser (without the electron wrapper), though, once the first node dependency is used.

Add to the export view created by #85.

• Prompt user for password before signing the transaction if a password is required
• Allow setting password on creating a new account

Nice to have: Show some info that the account is password protected (or that it's not if mainnet) on the account page.

While developing in web mode, the data should still be persisted.

Might become obsolete if #50 is solved. Minimal effort!

• Development build: Store data in local storage
• Production build: Don't allow production web builds without electron

Can delete account, but it's still visible in the account list afterwards. After refreshing the window it's fine, though.

As a user I want my data to be persisted. Right now it's just some volatile mock data.

Provide:

• Encrypt / decrypt passwords
• Save data to disk in electron app
  • Make sure it still works in the browser, though (for development)

• Create secret key QR for account export
• Scan secret key QR for account import
• Create payment request QRs
• Scan payment request QRs

Keep in mind the following edge cases:

• Account is not password-protected yet, user wants to set a password
• Account is password-protected, user wants to drop the password protection (not a critical use case)

As a user I want my keys to be securely stored on my local disk.

Have a look at: https://github.com/sindresorhus/electron-store

Add components that are otherwise difficult / inconvenient to test and components with a focus on reusability:

• Balance
• TransactionList
• TransactionSummary

Use render props instead (see here, for example)?

Example:

// instead of withBalance(options)(Component):
import BalanceSubscription from '../data/BalanceSubscription'

const ShowMyBalance = (props: { wallet: Wallet }) => {
  return (
    <BalanceSubscription publicKey={wallet.publicKey} testnet={wallet.testnet}>
      {(balance: number) => (
        <div>Your balance: {balance}</div>
      )}
    </BalanceSubscription>
  )
}

Feels more intuitive, is easier to read and type and is also conceptually closer to the underlying subscription functions.

As a user I want to be able to create a new account from scratch.

• "Add wallet" dialog:
  • should create wallet from scratch (create new private key)
  • should show a button to import an existing account

Try to match the frontend-boilerplate.

Use more intuitive naming. Consolidate the code that is shattered across components/Overlay/* and stores/overlays.

Keep in mind that the user might have to enter their password first.

Can .babelrc be safely deleted?

Show some nice splash screen for the few seconds the app loads. Ideally show it even before the browser view has initialized (splash screen implemented in electron main process, not in bundle).

Provide:

• Adding accounts
• Renaming accounts
• Deleting accounts
• Changing passwords