Embrace

The Embrace Developer Hub

Welcome to the Embrace developer hub. You'll find comprehensive guides and documentation to help you start working with Embrace as quickly as possible, as well as support if you get stuck. Let's jump right in!

Documentation

Getting Started with Embrace

This page will help you get started with Embrace. You'll be up and running in a jiffy!

Embrace partners with mobile teams to improve their in-app experience. While we provide value to everyone from business owners to CS to QA to engineers, the integration portion of the document is written with the mobile engineer in mind. An engineer is often handed a SDK without any context and asked to implement it via docs. We aim to make this easy with specific integration suggestions for the engineer so that Embrace can provide the most value to the entire mobile team. It's a group effort to improve the user experience and overall ROI.

Start Here -- Industry specific integrations
To get started, we built a few industry specific integrations to make life easy for you and to get the most out of Embrace. Please take a look:

For a complete set of instructions, please go to the full integration guides:


Dear Mobile Engineer,

First off, we know what it is like to be handed yet another SDK. Good news -- unlike other SDKs, Embrace has been built to help you, the engineer. Plug us in and get full visibility into your users and apps that you didn’t have before.

Embrace is the only performance monitoring platform focused solely on mobile. The team at Embrace have all built large-scale mobile apps (Whisper, Tinder, Walking Dead, WWE…) and what we wanted most of all was visibility into what was technically occurring and for specific users -- and we didn’t want to use ill-suited marketing/analytics tools and logging tools that required me to have impossible foresight into my future bugs.

Each of us experienced a user or CxO complaining. We wanted to be able to look the complainer up and see if it was their fault, a connectivity or environment issue, a SDK or perhaps the code. Plus we always had hunches that OOMs, poor speed of network calls from the client-side perspective (and not server,) broken purchase mechanisms, and other things made apps less stable. Why couldn’t I find this info simply and quickly?

Embrace was built to help the entire Mobile Team (CS, QA, Marketing, Product) but, most specifically, you the Engineer. We know every device is a user so we do not sample. Instead we let you look up any user in prod or dev, select any session (good or bad) and reproduce all the technical details of the experience. (We’ll even take screenshots when we identify an issue so you can see it!) Even for crashes, the solution is not always a line of code but the prior 10 seconds that lead up to an issue. Since we store and track tons of user level session data, we can aggregate user sessions to proactively identify and alert to all sub-optimal experiences, including OOMs, Freezes, Slows, Network errors, re-installs, voluntary terminations. (We could keep going...)

We are excited for you to integrate Embrace so we can make each user's experience better. We are focused on only mobile and have two integrations guides, Android and iOS. Each guide is designed to make the integration as quick as possible while achieving the highest value out of Embrace. And the best part is this -- integrations typically take just 15 minutes.

Getting Started with Embrace

This page will help you get started with Embrace. You'll be up and running in a jiffy!