The last view that is generally available within many social containers is not actually a view at all, but more of a view state. The default, or preview, view of an application displays content to users who have not already installed the application or to individuals who are currently logged out of the social network. This view is in public view space, and therefore, may not have direct access to much of a user’s profile information, similar to how the public badge provided through the user profile provides only a small subset of information about her.

This view state can emerge within any traditional view, including the profile and canvas view. The home view, however, is generally a personal profile for a logged-in user, so it is unlikely that the default state would emerge in that view. In the case of a signed-out user, you will not be able to take advantage of any personal information because it’s unknown. If this state emerges in a small view, it may simply be a case of someone trying to view a user’s profile; although your application will render, this event does not necessarily indicate a user who is engaged with it. If this state emerges within the application’s canvas view, though, you most likely have a user who is interested and wants to learn more.

For cases where this state emerges in the smaller views of an application, you should be providing a method to try to immediately drive the viewer to your application’s canvas view to install the application, or provide a method to engage with her and then drive her to the canvas view. Since the user has never interacted with the application and thus will not have entered personal information that you can leverage, it’s difficult to personalize this state. An engaging small view is important even in these cases, but your ultimate goal for the default view is to drive the user toward an install state and engage her.

When this state emerges in the larger canvas view, it’s likely that users are looking to see what the application is before committing to installing it. In this case, you should try to provide them with as much interaction with the application as possible while still pushing them to log in and install. Coupling the install state of the container with the functionality of the application is a good way to seamlessly add a new user. If the user begins interacting with the application’s controls and customizations, you can bring her to the container install state and walk her through installation to begin working with the application.