The SmartDownload System: It’s in the Details

The SmartDownload system works with your content in different ways depending on the scenario. Your content is being shared and viewed in different ways—we take that information and use it to optimize your app’s chances of being downloaded.

In this instance, let’s assume each entity is shared to the user’s Facebook wall. That post would contain the app icon, name and description, as well as several links to the entity’s SmartDownload page. Depending on what is being shared, and where it is being viewed, the SmartDownload page will display different content.

This is a comment on an entity that’s been shared to Facebook. The highlighted areas all link to the SmartDownload page.

Below is a list of different scenarios and how the SmartDownload system works with them.

Web View (default)

Every SmartDownload page will contain the following, no matter what:

  • Your app icon and a preview of your app’s market description.
  • A simulation of your app.
  • Links to your app’s iTunes and/or Google Play page (we can tell if you have both).
  • A QR code to scan your app.
  • Options to send the SmartDownload page to themselves or a friend via SMS and email.

1. If the app itself is the entity, there will be no extra content beyond what is listed above.

App as Entity.

2. If the entity is a piece of content with a valid URL, a preview of that content will be displayed with the option to continue to that URL. This URL is entered as the key, and we honor the metatags of that URL when linking to it. (You can even add custom meta fields to the entity’s SmartDownload page by adding a dict into the entity meta field.)

Entity with Valid URL.

3. If the entity is a piece of content without a valid URL, the entity title will be shown with a message to download the app in order to view it (no need to worry about error messages).

Entity Without Valid URL.

4. If the entity is an image with a valid URL as the key, the image will be displayed with the entity title.

Image as Entity with Valid URL.

5. If the entity is linked from an activity—for example, a comment on a video is shared—then the same rules apply as above depending on what that entity is. The difference is that the comment itself will then be displayed as well.

Entity Shared from Activity.

Mobile View

When the SmartDownload page is linked to on a mobile device, the user is taken to a page that directs them straight to the app in iTunes or Google Play—depending on what device they’re on.

1. If the app itself is the entity, they can either head to the market page or open the existing app if they have it. This is also the case if the entity shared does not have a valid URL as the key. These options are displayed instead of taking the user to a dead page.

App as Entity/Entity Without Valid URL.

2. If the entity does have a valid URL, the user is given the same choices with the additional option of continuing on to that content at the specified URL.

Entity with Valid URL.

Editing Your Settings

The SmartDownload system was designed to put your app in the prime position to draw in more downloads, without you having to lift a finger. But we know that you also have a specific vision for your user experience. Edit the way your content is handled and how users interact with the SmartDownload page in your settings.

Change the way your SmartDownload page looks (for both non-mobile and mobile views) by editing the page’s CSS.

Editing page design with CSS.

Create and edit widgets for your SmartDownload page with HTML.

Creating/editing HTML widgets.

In Advanced Settings, you can choose how your app and entities are shared (for mobile and non-mobile views).

Application Share.


Entity Share.


Application share refers to when the app itself is the entity being shared.

  • “Default” means users will be sent to the SmartDownload page.
  • “Always forward to the URL specified” means users will skip the SmartDownload page and go straight to a URL you’ll enter here. Something cool about this is that you can customize this URL with different parameters, to send users to different versions of that page.
  • “Skip to Apple/Android store when possible” means exactly what it sounds like. Since this is the non-mobile view, we won’t always be able to tell but will forward them to iTunes or Google Play when possible.

Entity share is when a piece of content within the app is the entity. The options for entity share are the same as application share, except for the addition of “Always forward to entity key URL if valid”. Choosing this forwards the user straight to the URL entered in for that entity’s key. If an entity doesn’t have a valid URL, the user will be forwarded to the SmartDownload page instead of an error page. We’ve got you covered!

The settings options for mobile are the same except that when “Skip to Apple/Android store when possible” is chosen for application share, the user will be forwarded to the store that correlates with the device they’re on.

There is one other setting in mobile—the ability to enter your app’s schema so the existing app can be found on a user’s device instead of taking them to the browser. Beyond this, adding the entity ID or entit key as the schema will render as the corresponding key or ID for the entity, which can be used to open the app to the specified piece of content for even smarter routing.

Schema Settings.

Here’s a quick overview of the SmartDownload settings and what you can do with them, for a more in-depth look:


That should cover most scenarios that involve the SmartDownload page. If you want a deeper look into the inner-workings of Socialize, feel free to check out our iOS, Android and API documentation.

Advanced Notes: Overriding SmartDownload entity content

If you woul like to override these settings when you create or update your entity from the app you can do so by pushing override keys within a dictionary object using the entities meta field. You can learn more about adding meta data to your entity through our API in our SDK documentation here: