If I reveal the mnemonic, I think it would be helpful to include underneath it the character/component pieces (the ones that are shown when you hit "i" . In this way I do not have to go to both places. And of course if I still want the comprehensive information, I can still press "i".

This would be convenient, but it doesn't work well in the case that things get too long. With the definition and mnemonic, we can shrink the text arbitrarily until long entries fit. With the decompositions, though, we still need one per line, and they wouldn't be very useful shrunk (as would often happen), unless we went to a scrolling solution, and scrolling sucks within modal areas like that. Maybe on the iPad layout, this can happen better.

There are some formatting characters (like *stars* for bold) that show up online but not on the iOS app. In fact they are removed in the app- would it be possible in a future version to add support for these？

Depending on where the bold and italics aren't showing up, it's either a bug on my list (top prompt area) or a limitation we can't easily code around (reading and definition prompts).

My problem is that I find that at least 50% of the time that I am looking at the mnemonic, I want to see those component parts, if for no other reason than to reinforce what they are.

And it is not always clear what character components are being referenced in a given mnemonic due to their freeform nature. Having the character component definitions on the same panel for reference makes it easier to put it all together.

As a user, I personally wouldn't mind scrolling. It would be infrequent, only be necessary if the mnemonic is unusually long. A user would never have to scroll if if their sole intent in entering the mnemonic screen is to just see the mnemonic (they can ignore the component definitions), or if they would just prefer to get the definitions by returning to the main study screen and pressing "i" .

As for autoscaling, this could be addressed using a minimum font size. In that way the text never gets too small. And if I have to scroll, then I scroll.

The way it is set up at the moment, you can view the mnemonic without seeing the character or its components, which I use as a 'hint' sometimes (I don't count this as 'remembered'). If everything appeared together this feature would be lost.

Or if there was a bit tighter integration with Pleco, perhaps there could be an icon that takes you directly yo Pleco's Character breakdown.

I'm happy with having to click on two separate things, one for mnemonics and one for detailed info; as alanmd says, many people use them to do different things.

The main thing is, I would like to see my own mnemonics. Is that too hard to link up/download?

You should be seeing your own mnemonics, Catherine; they are synced between the app and the site, whether you pick a mnemonic on the site or write your own in either place. Is it not working?

Huh, that's weird then. I was sure I was seeing other people's, but maybe it was for similar characters that I actually hadn't written one for. I didn't check properly before posting, sorry!

You do see other peoples' mnemonics for anything where you haven't chosen a mnemonic, although you're only able to see the top mnemonic (and then only if it has a few votes).

"Depending on where the bold and italics aren't showing up, it's either a bug on my list (top prompt area) or a limitation we can't easily code around (reading and definition prompts)."

The mnemonic and definition areas now allow *bold* and _italic_ formatting (I think this might have been the bug fix that you mentioned) - thanks!

Nick, for the decomposition question (at the top of this thread), perhaps it can be implemented in the iPad version. I like the iPad version, but I hope that hope that you can make better use of all that real-estate as you continue to develop the app.

For the decompositions, it can be a little "tray" on the right (or left) hand side of the top prompt area. If you click on the tray handle, the decomposition would slide out, and thus you should have enough lines to handle most decompositions (and there's enough space to extend the prompt area downward anyway, or you can scroll this try.

iPhone is obviously impractical.