To be honest, if we were a lot bigger and / or didn't have such an enthusiastic customer base we wouldn't have released any of these betas, we would have waited until we had something that was feature-complete and nearly bug-free, put that out or a month or two of tweaking / compatibility-checking and then hopefully had a finished version. But we were getting enough e-mails literally pleading with us to just release something, however buggy, so that people could get access to a few of the must-have new features (like a C-C dictionary and audio) that we decided to go ahead and release something very early even though it's barely usable yet.
For our purposes, it really doesn't make sense to go through and worry about crashing bugs / compatibility issues / etc until we've got all of the features / interfaces fully implemented; otherwise we'll end up spending lots of time finding / fixing problems that will reappear (or need to be fixed again in an entirely different way) once we add some other missing feature. Hence the lack of stability improvements from Beta 1 to Beta 3. So I'm sorry you decided to try Beta 3; the reason it's posted in that separate thread is because it's so very buggy on Palm (I should put an extra note in about that, actually) and at least half of the people trying it have had experiences similar to yours. We'll certainly make it widely known once we have a beta that we actually think is stable, but for right now it probably does make sense to just clear up everything and stick with the stable version.
Re your feedback, Preferences are definitely going to get cleaned up and many of them indeed do not work at all now, and most of the reader buttons aren't implemented yet either - this is another example of releasing betas not really fitting with our development cycle, it's a waste of time to implement the user interface for something when the underlying design might change. Not sure what's going on with that palette selection screen, that actually does seem to work on our TX here. With Info, are you sure you installed the Unihan character reference database? If that's not installed that could definitely cause Info to crash... potentially might happen on Stroke Order too if that's not installed/unlocked though it should be fine as long as you don't switch into that tab.
For our purposes, it really doesn't make sense to go through and worry about crashing bugs / compatibility issues / etc until we've got all of the features / interfaces fully implemented; otherwise we'll end up spending lots of time finding / fixing problems that will reappear (or need to be fixed again in an entirely different way) once we add some other missing feature. Hence the lack of stability improvements from Beta 1 to Beta 3. So I'm sorry you decided to try Beta 3; the reason it's posted in that separate thread is because it's so very buggy on Palm (I should put an extra note in about that, actually) and at least half of the people trying it have had experiences similar to yours. We'll certainly make it widely known once we have a beta that we actually think is stable, but for right now it probably does make sense to just clear up everything and stick with the stable version.
Re your feedback, Preferences are definitely going to get cleaned up and many of them indeed do not work at all now, and most of the reader buttons aren't implemented yet either - this is another example of releasing betas not really fitting with our development cycle, it's a waste of time to implement the user interface for something when the underlying design might change. Not sure what's going on with that palette selection screen, that actually does seem to work on our TX here. With Info, are you sure you installed the Unihan character reference database? If that's not installed that could definitely cause Info to crash... potentially might happen on Stroke Order too if that's not installed/unlocked though it should be fine as long as you don't switch into that tab.