Serializable works but you should avoid this one due to performance reasons. Proper serializable objects do too much work and have too much overhead for what you most likely need.
If you design you own objects, use Parecelable instead. If you have to deal with objects from 3rd party libraries that are Serializable, this choice has been made for you :), although you could still embed them into a Parcelable and save/restore them yourselves. On Friday, September 21, 2012 11:17:24 AM UTC-4, LemonCodes wrote: > > What is the best practices in passing Object? is it serializable or > parceable? kinda confused which one to use, i'm just planning passing a > single object not an array of Objects > -- 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
