YoshiCookie - thanks for all of the suggestions!
#1 we actually do have a popup dictionary in the web browser, though it's a bit experimental at the moment (sometimes screws up the formatting of web pages) - go to Settings / Reader and turn on "Enable on web" under "Live Mode," then tap on the "Live" tab above the (opened) address bar in the web browser to enable it on a particular page. As I said, it's experimental / buggy, but we're steadily improving it (fixed a few bugs in it in the soon-to-be-released 2.1.1 for example) and it's generally running better on newer / faster / higher-RAM iDevices.
Which part of the built-in web browser interface are you having problems with? We know we aren't going to get it as nice-looking as Safari, but if there's some part of it that you find particularly unpleasant we're always looking for ways to improve.
#2 no comment yet except to say that the 5 megapixel camera in the iPhone 4 will do wonders for this possibility. (makes a significant difference compared to the camera on the 3GS, and the one on the original 3G would be basically useless for OCRing anything smaller than a street sign)
#3 in general I don't like making our offline software too dependent on online resources - people grow to rely on them and forget that they're not always available - but we're certainly always looking for more dictionaries to license / more open-source ones to convert; C-J I don't think it likely to come cheap licensing-wise, though, given the size of that market in general.
#4 customizable fonts are easily doable on both the iPad and on iPhone OS 4.0 devices, so you may get your wish on that. Actual etymology I'm not sure about - a lot of the information out there is old / highly debatable, and there are too many 形声字 for which story-based memorization doesn't work, so as a learning tool I tend to think you're better off with something like Heisig or Tuttle Learning Chinese Characters.
On #5, Simplified / Traditional switching in Char Info is a bit dicey since the software doesn't always know what the correct traditional character is (e.g. if you're accessing that screen from the document reader) - good point on linking between Unihan fields, though, we ought to be able to make those tappable for cross-referencing.
#1 we actually do have a popup dictionary in the web browser, though it's a bit experimental at the moment (sometimes screws up the formatting of web pages) - go to Settings / Reader and turn on "Enable on web" under "Live Mode," then tap on the "Live" tab above the (opened) address bar in the web browser to enable it on a particular page. As I said, it's experimental / buggy, but we're steadily improving it (fixed a few bugs in it in the soon-to-be-released 2.1.1 for example) and it's generally running better on newer / faster / higher-RAM iDevices.
Which part of the built-in web browser interface are you having problems with? We know we aren't going to get it as nice-looking as Safari, but if there's some part of it that you find particularly unpleasant we're always looking for ways to improve.
#2 no comment yet except to say that the 5 megapixel camera in the iPhone 4 will do wonders for this possibility. (makes a significant difference compared to the camera on the 3GS, and the one on the original 3G would be basically useless for OCRing anything smaller than a street sign)
#3 in general I don't like making our offline software too dependent on online resources - people grow to rely on them and forget that they're not always available - but we're certainly always looking for more dictionaries to license / more open-source ones to convert; C-J I don't think it likely to come cheap licensing-wise, though, given the size of that market in general.
#4 customizable fonts are easily doable on both the iPad and on iPhone OS 4.0 devices, so you may get your wish on that. Actual etymology I'm not sure about - a lot of the information out there is old / highly debatable, and there are too many 形声字 for which story-based memorization doesn't work, so as a learning tool I tend to think you're better off with something like Heisig or Tuttle Learning Chinese Characters.
On #5, Simplified / Traditional switching in Char Info is a bit dicey since the software doesn't always know what the correct traditional character is (e.g. if you're accessing that screen from the document reader) - good point on linking between Unihan fields, though, we ought to be able to make those tappable for cross-referencing.
