Recommendations are always being created, and recco builds profiles of the people using it to predict what future content will be most interesting. Then new content is created and made available. We create content by a combination of reviewing high value health materials in the public domain, summarizing or interpreting that content in our recommendations, and then evaluating the existing recommendations for how often they are viewed, liked, or passed over. Content that does not seem to resonate with users will be updated or removed so that we are only keeping high value content.

There are thousands of pieces of content on Recco, and more is added daily. We do not want to overwhelm people with content, or create doom-scrolling, so we will release content to people over time. As people interact with different content types and subjects, this informs what they will see in future use of Recco.

The integration is intended to be quite simple. It starts with our team creating a primary user account for your team to access the Back-Office for recco. This is where you can create apps and add other team users to access the system. From the Back-Office you can create keys that you will use to access recco from your applications. You will then load the SDK into your application with a short code snippet, and indicate the button or other interface element that will kick off recco by linking to recco from that element. Then you build your app file and you are ready to release. This will typically take around 15 minutes in total.

Recco supports video, image, and text content. Typically a user will see predominantly text with images as we are getting to know their interests, and then videos are thoughtfully displayed in the mix depending on the preferences and engagement of the person viewing the content.