One challenge for even experienced Marketing Ops teams when they start to introduce their mobile push strategy is determining which push notification provider to partner with for delivery, and then how to thread that provider’s SDK into their app. It’s a tough question for a variety of reasons, one of them being that they often don’t even know they may not need to bother with the second part at all.
When we rolled out support for sending push notifications earlier this year, the big differentiator for us was that we are offering an alternative to the SDK for those who need it. But, even when we tell first-time users that, we often get the question: What is the MessageGears SDK-less solution, and how is it different from other vendors?
The mechanics of how push notifications get sent are a little confusing. However, when stripped down to its core, there are a few basic differences between how we send push notifications that make MessageGears stand out. First, let’s dig in a bit as to why the presence or absence of an SDK matters, and then we’ll look at why going SDK-less could be an attractive option for a lot of teams.