Having been "forced" to enable install-to-SD for a couple of apps which feature widgets, this is a bit of a sore spot with me. I say "forced" because the average user doesn't understand the issues involved, only understands that you (the dev) haven't enabled install-to-SD, so they downrate you for it. Then other average users downrate you because their "widgets disappeared." It's a no-win situation.
I think your reading of the docs is correct, that the only downside currently is that appwidgets do get removed if/when the app gets moved to SD. As to whether more serious problems may arise in the future, who can say? Probably nobody at this point, and those who might (the framework team) won't, because they basically aren't allowed to talk about future plans. My preference would be for the system to ask the user before it moves an app with widgets to the SD card, or (at the very least) warns the user of these consequences if they move an app manually. Unfortunately, this change would have to be made at the system level, and somehow it doesn't seem likely. As a workaround, I'm currently in the process of implementing a warning of my own in the app's main activity. It'll check to see if it's been installed to SD, and if it has, issue a warning of its own. That's suboptimal - there's no guarantee the user will open the main activity in a timely manner to see this warning - but it's better than nothing, and will hopefully reduce the 1* Market comments. As it stands, I can stomach informing users that it's either > run-from-sd-card OR show widgets but NOT both. How are you planning to inform your users of this? Be aware that I already have it in my Market description, but most users don't read that. String -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
