We are warning when exporting a key (not when importing), which I think is the right place...
We are going to add a special "cold storage spending" wizard, which will not store the key on the phone (no more add-key + spend + delete-key). The key will only be in memory while making the transaction.

I see. Will add a scrollbar or find another solution when entering pin in horizontal mode.

Thanks for the feedback

Thanks for the through feedback. Much appreciated. This is vacation week for me. I'll get to work on your suggestions next week.


This is the case on some phones, I haven't seen it myself though. Initially the barcode scanner was external, but for security reasons (and ease of installation) we have embedded the Zxing barcode scanner. For some reason the app claims the name of the barcode scanner instead of Mycelium. Will investigate and fix. Is the app icon on your phone that of the barcode scanner or is it the Mycelium logo?


Right now you are working on one key at a time, and we are changing that. Many users have requested an aggregated view of all keys, and this is also what you see in other wallets. We are still in beta and collecting feedback

Link?

There has been much tweaking and fiddling with swiping to make it visually apparent. Still nobody (except me) like the way it works now. I'll give it another stab.
 

Will fix.


"Set Label" sets the label of the currently selected key or address. Will get refactored once we go to "aggregated key view".


Will add the others


I have been working on adding an "Add" button, which allows you to add an address by scanning or from clipboard. Will make it for next release.
 
By payments I guess you mean the address.
Have you really ever entered an address manually? How long time did it take to do it right? I haven't, and it is bound to be a huge pain, especially on an android device.
Andreas and I have discussed this quite a few times. His thinking is that we should allow for firstbits and address shorteners such as http://payb.tc/
It will probably not be in the next few releases.
Great feedback, keep it coming 

Yes
I was at the Mycelium booth just on the other side of the aisle all three days of the conference and didn't get a chance to see it. I guess that's my own fault.
Here it how it is currently done with the Mycelium Bitcoin Wallet (in beta): http://www.youtube.com/watch?v=W7V2myIwAuE
Since it is on a smartphone I prefer to use QR-codes. I'll probably add the option to request a device generated password. Do you have a spec for how the armory wallet backup is generated?

How to export your private key to paper without using a virus infected computer: http://www.youtube.com/watch?v=W7V2myIwAuE

Correct. If you mimic the serialization used by the Java implementation you will be golden.
The server is running at RackSpace, and is also used by BitcoinSpinner. Right now a lot of things are shifting in this space now that the Mycelium Bitcoin Wallet is marching through its beta. Eventually the BCCAPI will be retired.

Sorry for reviving this thread...


I am not fond of brain wallets for many reasons (users are notoriously bad at choosing strong passwords, they are easily forgotten, you can attempt a brute force once the address hits the network, etc...)

However, I like ErebusBat's idea of letting software pick a strong password to be displayed in addition to print out an encrypted secret on paper:
 - The password wil be strong
 - The user has no choice but to write it down, but can choose to write it down on a separate sheet.
 - Unlike brain wallets, it is not feasible to brute force until you have the secret stored on paper

I would however still let the user choose to store the secret in plain on paper, and have this as an alternative option.

I see.
For some reason I was certain that you sent it to the address in your clipboard.
I'll add a warning for the other use-case as well. I am going on vacation Friday morning, but will see if I can get it in before that. If Andreas spins a release while I am gone it will appear there.

The seed used for generating the private key is stored in a file stored in app private storage. To get to it you have to root your device or somehow mount it and look for a 'KeyManagerCache' preferences file.
On my device it is located here: /data/data/com.miracleas.bitcoin_spinner/shared_prefs/KeyManagerCache.xml
Once you have access to the files you should be able to copy them to another phone where BitcoinSpinner is installed. Then it should assume the other apps 'identity' along with keys and everything. I haven't tried this myself, as I always make paper backups 

Yes it is 

The warning is shown in red on the send summary page just before you sign and send the transaction.
Here are my steps to reproduce:

• Install 0.5.3
• import key with funds
• import bitcoin address (or create random key + address, then delete key)
• open bitcoin address, click QR code, copy to clipboard
• open key with funds
• send -> Clipboard-> enter amount -> Warning shown on summary page

Warning: You are monitoring this address, but you cannot spend coins from it unless you have the private key elsewhere.

Version 0.5.3 is available in the app store:

• Import BitcoinSpinner backups (We could already import BitcoinSpinner exported private keys)
• Improved contrast in transaction details -> easier to read in sun light
• Added warning when sending funds to a read-only address in your wallet
• Modified sorting in Keys & Addresses: Keys on the top, Addresses at the bottom, both categories sorted by timestamp
• Disabling Export button after successful export to SD card
• No longer forcing the user to choose a folder when exporting to SD card (SD card must have a 'mycelium-export' folder)

Thanks for the feedback. Keep it coming so we can exit beta faster.

Changes so far in the next update:

• Added add-to-address-book button on send summary
• Displaying name of receiver in send summary for receivers in address book
• Made back-button in Keys & Addresses take you to balance view instead of quitting
• Fixed an issue that made the app appear sluggish in most views (you will notice that one)
• Properly centering of "Show to Sender" text when receiving coins

Yes, I see. I have been sitting in the dark during development... need more light and fresh air I guess :-)
I don't want to display buttons, but wanted users to know that they could click hashes / addresses, so I went for making it appear as a link. I'll play around with the colors and make them somewhat lighter.... and dare a step into the sun for testing.

Yes you are right, the wallet does not use deterministic keys. When you design a wallet for a device with limited screen capabilities and broad adoption you have to make some tough choices about usability. If you want both deterministic keys (all keys derived from some seed) and key import functionality you basically have two different key management mechanisms. This is IMO to much unless you want to make a tool for geeks only. Since I have been asked many many times to include key import in BitcoinSpinner I chose this model.

Regarding the warning on receiving: I agree, I'll add it 

The problem is that you have everything in one screen, which is confusing and clutters up the very limited space that we have available on small devices. With the Mycelium wallet you have the option to choose fiat balance, with BitcoinSpinner the UI would get (even more) clumsy if you added that.

I'll lock this thread to let the discussion continue in the dev thread here: https://bitcointalk.org/index.php?topic=53353
We are busy discussing the Mycelium Bitcoin Wallet over there... the successor of BitcoinSpinner, come join us.

Good ideas, I'l add them to our list

The way the Mycelium wallet works right now is that you work with one key at a time. This means that balance, transaction history, sending/receiving all works on the currently selected key or address. This gives you fine-grained control over your keys, and that has its merits. We have been thinking about changing that to a model where keys/addresses are treated as a pool. This has the following consequences:

• Balance: The combined balance of all your keys and addresses (address = 'read-only wallet')
• Transaction History: The combined history of your keys and addresses
• Sending: Spend from the sum of funds available to your keys, addresses ignored
• Receiving: Your default receiving address will be used. You will select which in the Keys & Addresses view.

While the above is all nice, it also means that you will have less control when accessing your cold-storage (import key / spend / delete key), as the key will be part of the list of other keys and you may do a spend from several addresses. To alleviate that a special single key mode has to be made while not cluttering up the UI.
If more people ask for it we may make the change.

Good ideas, I'l add them to our list

The way the Mycelium wallet works right now is that you work with one key at a time. This means that balance, transaction history, sending/receiving all works on the currently selected key or address. This gives you fine-grained control over your keys, and that has its merits. We have been thinking about changing that to a model where keys/addresses are treated as a pool. This has the following consequences:

• Balance: The combined balance of all your keys and addresses (address = 'read-only wallet')
• Transaction History: The combined history of your keys and addresses
• Sending: Spend from the sum of funds available to your keys, addresses ignored
• Receiving: Your default receiving address will be used. You will select which in the Keys & Addresses view.

While the above is all nice, it also means that you will have less control when accessing your cold-storage (import key / spend / delete key), as the key will be part of the list of other keys and you may do a spend from several addresses. To alleviate that a special single key mode has to be made while not cluttering up the UI.
If more people ask for it we may make the change.

Hey Giszmo,
I was looking forward to some feedback from you. Great to see that you like it so far, and I agree on your thoughts on first impressions. So let me sum it up a bit.

General comment: We are trying really hard to make this wallet easy to use. So features that are useful for the 1% hard-core bitcoiners and confusing to the rest are not going to make it. We want to have as few settings/options as possible while having a feature rich wallet. This is a tough balance.

1. Shuffle/Use on key creation: Since you understood the UI after half a second I think we got it spot on.
2. Vanitygen-ing keys: Phones are awfully slow at this even with just 3 letters, and it really is a special use-case. I think it is best to leave it as something hardcore bitcoiners do on powerful computers, and then import them into Mycelium.
3. Swipe delay: I agree. On older phones it feels sluggish when you swipe left/right. We have discussed this internally and we have some ideas on hoe to improve it.
4. Redundant servers: Like BitcoinSpinner, Mycelium depends on a custom made super node which is not open source. The company (also called Mycelium) has invested heavily in developing it and we are going to use it for other projects (hint: for instance bitcoincard.org) and commercial services. Unlike BitcoinSpinner the Mycelium wallet is backed by two 100% redundant physical servers in two different datacenters. Whenever the wallet makes a query to get its balance, get unspent outputs, transaction history etc it connects to random server (SSL encrypted with certificate pinning). If it does not respond it chooses the next. This way the wallet continues to work while a server is down for maintenance/upgrades. The Spinner server was down 3 hours yesterday because the hosting provider chose to do some maintenance (first downtime for months). With Mycelium this is a lot less likely.
5. Should I use Mycelium instead of Spinner: Mycelium is in beta (so is the Spinner by the way along with most things in bitcoin land ). We are doing our best to make sure that it has no bugs and has 100% uptime. However, at the stage we are at right now we are requesting feedback, improving things, fixing bugs etc. I think you should test it and judge for yourself. I have used the Mycelium wallet hundreds of times and sent transactions worth more than $1000 with it and didn't loose a coin so far. A few weeks from now I would definitely say that you should use Mycelium. Eventually Spinner will be phased out
6. Enter amount to send before scanning: The thing is that often the QR-code contains the amount to send. In those cases we can skip the entering-amount step entirely. If we did it the other way around you would have to enter an amount, then scan a QR-code, which may overwrite your amount. Too confusing and IMO leads to mistakes.
7. Enter label on the send screen: Some wallets always present a dialog asking you whether you want to add the address to your address book just before/after you send the transaction. This is totally annoying, and I don't remember ever using it. If more people ask for it I would probably add second button along with the send button for that finctionality. Annoying dialogs are annoying ;-)
8. Open sourcing servers: As mentioned in 4. we don't have any current plans of open sourcing the server. grau has made an open source server with similar capabilities (bitsofproof.org) and is making a living on running it as a service.
 

Thanks!

Yeah, quite a bit has been thrown at it since you saw the prototype at the conference.
It is great to have it in the open and get feedback.

Here it is: https://play.google.com/store/apps/details?id=com.mycelium.wallet