Agreed. The intended use case for move to sd was for games or multimedia applications, but I see users wanting to move even small applications.
It's actually a valid case for applications that have large code, or use a large amount of data / cache storage (so move to sd makes sense), and also have a widget or a service. For widgets, the home screen could indicate that the widget is disabled, similar to how it already does for missing widget providers (the "cannot load gadget" message", btw, shouldn't that be "widget"?). This is already better than removing it from the home screen without any indication whatsoever. The launcher could also keep the RemoteViews until the memory card is again available, and then reinstate the widget to full working state. It already does almost the same thing on orientation changes. For services, it would have been possible to listen for ACTION_EXTERNAL_APPLICATIONS_AVAILABLE and restart your service / reset your alarms then, execept that the affected applications do not receive this broadcast (I don't understand why, so I must be missing something). -- Kostya 2011/1/16 Jonas Petersson <[email protected]> > On 01/16/2011 12:21 PM, Zsolt Vasvari wrote: > >> I agree. A "smart" user wouldn't complain in the first place about >> not having the "Move to SD card" option for a 1MB app. >> > > Opinion: It would be nice if the "Move to SD card"-function could detect > that the application requests for instance BOOT_COMPLETED or has a widget > etc and inform the user that those functions will no longer work as expected > if the move is completed. This assumes that the application isn't installed > on the SD by default and that the user understands the warning so I'm not > really holding my breath for it. > > I guess the best you can do as a developer is to detect that the app is > running from SD and inform the user about the drawbacks on the next start. > Hardly ideal, but better than nothing. At least the explanation can then be > very specific as opposed to what a generic function would have to state. > > As with many apps, it is not obvious that the automatic startup or widget > function is a critical function of the application, it may just be a nice > frill that is seldom used (I know my self that I really only ever use ONE > widget and that one has no other function than being a widget - it shows the > next few calendar items). > > My few cents / Jonas > > > On Jan 16, 6:12 pm, Marcin Orlowski<[email protected]> wrote: >> >>> On 16 January 2011 07:49, Dianne Hackborn<[email protected]> wrote: >>> >>> Sorry, you can point them to that documentation if you want. This is a >>>> pretty fundamental aspect of the behavior of the SD card. >>>> >>> >>> Are you kidding? I'd say that forseeing such user behaviour is pretty >>> fundamental when you design anything. It'd not hurt too add a warning >>> popup telling user to confirm "move to sd card" and ack s/he >>> understand the risk of certain features of the app (which can easlily >>> be told in most cases based on app's Manifest) simply just won't work. >>> Assuming users are by default smart not stupid is stupid, not smart. >>> >> >> > -- > 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- 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
