We are looking to set up PUSH and web in-app but are wondering if we should use Customerios SDKs, or go with a home built solution, do you have any recommendations on features and such?
Solved
Why Customerio mobile SDKs?
Best answer by Rachel
Here there,
Here are some of the features of our SDKs:
- Open-source SDKs. MIT licensed.
- Up-to-date with the latest iOS and Android versions.
- Strict semantic versioning for calm version upgrades.
- Small in size. Only install what you need and avoid bloatware.
- Designed with automated testing in mind. Mocking + dependency injection-friendly.
- Fully documented, covering everything from implementation to common use cases.
- Snapshot builds and quick releases. Wait less time for fixes.
- Real-world sample app available for reference.
- Easy to set up, flexible to customize your unique use cases.
- Published on Maven Central.
- Written in Kotlin, for Kotlin (with Java support as needed).
- Written in Swift, for Swift (with Objective-C support as needed).
Additionally, there are some long term benefits to use the Customer.io SDks:
✨ Have less code in your app & fewer error messages taking up your time
- Customer.io can see the payloads coming through so we know exactly how to help
🔥 Allow your marketing team to work independently
- After the initial set up of the SDK, your marketing team will be able to easily build messages inside Customer.io without engineering resources
- Engineers will no longer be needed to troubleshoot a PUSH AND our in house technical support team can assist with any issues that arise.
📈 Measure your conversion rate within Customer.io by knowing exactly how many people saw your PUSH with device data.
- New features: Capture device data like “push enabled” to use in your messaging strategy
Hopefully that assist in your decision. Thanks so much!
Reply
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.