Lock in $30 Savings on PRO—Offer Ends Soon! ⏳

Chat apps: my observations based on 2 projects...

Chat apps: my observations based on 2 projects and 3 chat services

Avatar for Lukasz Pikor

Lukasz Pikor

October 12, 2018
Tweet

More Decks by Lukasz Pikor

Other Decks in Programming

Transcript

  1. Chat apps: my observations based on 2 projects and 3

    chat services Chat apps: my observations based on 2 projects and 3 chat services
  2. Chat apps: my observations based on 2 projects and 3

    chat services My experience: Project A + SendBird: small app, small user base Project B + Layer: large app, large user base Project B + Twilio: work in-progress
  3. Services PubNub • Two products: ChatEngine & Realtime Messaging SDK

    • Docs: hard to navigate, hard to read • Bot that works with IBM Watson • Learning curve • Big clients (Atlassian, Yelp, Adobe, HubSpot, Yahoo)
  4. Services Firebase • Sync your chat messages between millions of

    users with the Firebase Realtime Database. Seamlessly authenticate with Firebase Authentication, then set up a chat room in the Realtime Database. Messages appear on all your users’ devices in realtime. Use Firebase Cloud Messaging to send notifications so that your users get new messages if they’re in another app. • Receive images in existing messages Add code that downloads images from Firebase Storage.
  5. Services SendBird • Good SDK, very good documentation • Available

    through CocoaPods & Carthage • For sure good for small user base. Large user base is a question mark • Multimedia support: SendBird or your own solution • Supports migration from different platform
  6. Services Twilio • Easy to navigate documentation, but not everything

    is covered there. It’s worth reading Chat Overview document • Some SDK architectural patterns are surprising • TCHCHannels ➡ TCHMembers ➡ get(TCHMemberPaginatorCompletion) • Some differences between iOS and Android SDK’s • Available through CocoaPods & Carthage • Should be good for large user base (Airbnb, Uber, eBay, Hulu) amongst clients • Supports media messages, however in beta • Supports bots • Well known brand
  7. Services Layer • Can handle big conference • Has UI

    Library (while other services don’t) • Has built-in local cache & supports offline • Does most of the things for you • So why we decided to move from Layer to Twilio?
  8. UI