Break out of the app store. Parse (by Facebook) is a preferred backend provider for Twilio, the premier telephony service. By combining Parse and Twilio you can create a wide variety of applications which span SMS, web, mobile apps and more.
2. What is an App?
Think outside the 4” box
Modern apps are in the cloud
The cloud has no home button
The cloud never sleeps
The cloud is complicated
Your App Here
5. Twilio + Parse
Cross platform clouds are awesome
Cross-media clouds are awesomer
Twilio provides reach, delivery, and events
Parse provides persistence, logic, and native
apps
6. SMS or App
Apps have a custom experience
Apps are bespoke
Apps have high acquisition costs
SMS is universal
SMS is far reaching
SMS is guaranteed
7. Four different ways
SMS or App
Exclusive SMS is the App
Hybrid Apps require SMS for core features
Parity SMS or App are portals to the same
experience
Segmentation Different roles have different
environments
8. AnyQs: A Twilio + Parse app to handle Q&A
Building a Segmented App
A quick afternoon hack on Twilio + Parse
Audience members ask questions via SMS
Web app allows moderators to approve or reject
Native app for presenter to review questions
9. Data Model
Pending
Class Structure State Machine
RejectedAccepted
Answere
d
Question
to: string
from: string
prompt: string
state: string
10. Cloud Code in Depth
Data HostingCloud Modules
Functions Background Jobs
23. Hack Ideas
Push + SMS chatroom
SMS password reset
SMS alerts on data streams
SMS voting + Parse Analytics
Editor's Notes
Parse is a Backend as a Service, which is fancy speak for “a cloud you can rent.” What is the cloud?
A great cloud breaks platform boundaries, which we do
Exclusive: Group chat. Very broad reach but potentially limited. Parse provides logic.
Hybrid: 2-factor authentication, log-in by SMS secret. Really cool ideas, but often too niche for us to walkthrough
Parity: A chat client that has SMS or native apps, Facebook and Twitter are both accessible by SMS
Segmentation:
* Internet of Things (auto-SMS, passive or active clients)
* Call center
* TV voting
User sends an SMS to a Twilio number
Twilio sends POST to our RESTful API hosted by Cloud Code
Cloud Hosting (Could use simpler method, but then we need credentials in the URI) stores the question into Parse Data
Execute a Query for Parse Data
List all Questions where state == “pending”
Click on buttons to set state to “accepted” or “rejected”
Cloud Code afterSave trigger tells rejected users they were rejected via the Twilio Cloud Code Module
In a swanky app, afterSave trigger would send a push to speakers when the question is accepted
Execute a Query for Parse Data
List all Questions where state == “pending”
Click on buttons to set state to “accepted” or “rejected”
Cloud Code afterSave trigger tells rejected users they were rejected via the Twilio Cloud Code Module
In a swanky app, afterSave trigger would send a push to speakers when the question is accepted