Most applications have some preferences or user preferences that can be saved through SharedPreferences. My first implementation of user activity for editing his settings was quite simple: several input fields and the "Save" button. It is neither beautiful nor easily extensible.
Android system preferences and many of the applications I've seen tend to plan their edit preferences in ListViews.
My second approach is trying to emulate this: ListActivity, and each element must provide its own layout, since I want to store different types of values (some of them are numbers, some are logical switches).
I find it rather cumbersome to implement this, and now I wonder if there is any obvious design scheme missing here?
source
share