OpenSocial Required Fields
If your gadget is taking advantage of OpenSocial functionalities and is therefore declared as a social gadget with 'opensocial-x.x' as required:
you might consider restricting the vCard fields your gadget is requesting from the user's personal data. The available field names are
Applied in a gadget.xml snipplet, requesting the fields gender, emails, and the thumbnail URL will look as follows
<Require feature="opensocial-0.8"> <RequiredFields> <Field>gender</Field> <Field>emails</Field> <Field>thumbnailUrl</Field> </RequiredFields> </Require>
The following fields will be available right away since they are within the implicit minimal field requirements
However, including one or more of these fields within the 'RequiredFields' section will enhance the user experience by not showing unused information during the gadget installation process. Conclusion: Always specify your field requirements!
What's in for me?
Specifying your field requirements upfront has the following advantages
- Higher conversion rate
- During installation only the requested fields will be shown. The less fields he/she is asked to fill out, the more likely he/she will install your gadget as opposed to leave the installation process because of being overwhelmed by too many questions.
- You can ask for more at any time
- If your business logic changes or you want to ask the user's permission for other fields any time later, you can simply request those fields in future. The user will only be asked to fill out the field(s) you ask for as complementary data to the already existing information.
- Enhanced transparency for your users.
- Providing required field information is not mandatory yet but may become mandatory in future
- The example described above will only work within a <Require feature="opensocial-x.x" /> section
- The former RequiredDate attribute within the ModulePrefs section is now deprecated