Best Practices for Recommendations
The following are best practices for creating recommendations.
- Understand the Difference Between Recommendations and Notifications
- Personalize the Notifications to the User
- Delete Stale Cards
- Don't Exceed the Notifications Limit
- Limit the Number of Recommendations Shown at One Time
- Sending Recommendation as a Background App
- Handling Back Button Events
- Provide Free, Friendly Content
- Next Steps
Understand the Difference Between Recommendations and Notifications
- Recommendations try to guide users to content they might enjoy. The recommendations are based on prior the user's history, new content available, or related content.
- Notifications let users know about updates associated with your app. These updates might include new functionality, new levels, new release versions, changes in the app, or new badges earned.
Personalize the Notifications to the User
Recommendations are most effective when you personalize them based on user profiles. The best recommendations look at your users' interests, profile, and recent activity to come up with the recommendation. Personalizing recommendations leads to greater engagement and interest in your app.
Delete Stale Cards
Keep your recommendations fresh and inviting by deleting old cards. Track what content has been shown and visited before so you can delete it later. For example, if the user finishes watching the recommended content, delete it from the recommendation row.
If you continue to send stale recommendations, users might actually uninstall your app.
Don't Exceed the Notifications Limit
If you exceed 50 notifications, you may see errors such as the following:
W/NotificationManager﹕ notify: id corrupted: sent 51, got back 0.
Because of this limit, you should cancel older notifications before sending new notifications (if the number exceeds 50).
Limit the Number of Recommendations Shown at One Time
Avoid sending too many recommendations at once. Consider batching recommendations together in smaller groups of 5 at a time.
Sending Recommendation as a Background App
Some apps choose to send recommendations as a background process. Note that the background processes can be killed if the system exceeds the available memory.
Consider using trigger points to send recommendations instead. The trigger points could send recommendations using an
AlarmManager at repeating intervals. The repeating intervals can be expired using an Android
Sync adapter task.
Handling Back Button Events
When users press the Back button, your app should self-destroy and return to the recommendations row on the Amazon Fire TV home screen. (The return point should be where the application was launched when the user clicked a recommendation.)
Provide Free, Friendly Content
As a best practice, consider sending free content to the recommendations row. After the user opens your app, then you can push more premium/paid content.
Your app should not harass, hard sell, or recommend inappropriate content. Doing so will result in potentially being put on a deny list for your app.
To learn more, see the following: