Why : You get a big contract for 50 users , they will all use their mobile, their database is full of custom fields and they change their mind all the time. Let say they want 10 custom fields added to the contact view on their mobile. You will have to get all their phones (50) and go thru the process of adding the fields manualy... this is crazy ! Seriously , think about how complicated it can be to gert access to 50 phones !
Solution : From the installed version of AFW on the server you can create a different layout for every user, you can copy a layout to easely create 50 of them for different users. So basicaly, preferences need to be stored on the server instead of the phone, so when someone change phone he can just login on is new phone and start to work.
This is a real life situation we are facing right now and i'm pretty sure we will face this again soon with other client.