Chat platforms are continuing to grow at an accelerated pace as product owners are expanding their services to chat. “Be where your users are” is a motto that many companies are practicing and chat is one of those platforms where it makes it easier for users to use these services.
As the chat platform expands, the availability of libraries, examples, and experience around these platforms is slow to catch up. Frameworks like Rails and Laravel help developers get their services onto the web in record speed but these types of frameworks do not exist for chat platforms. That lack of availability can leave chat developers to re-invent the common capabilities which slows down development on the chat platforms.
Why can’t we develop for chat platforms like we do for the web or for mobile? Why can’t we get further away from the metal and build more rapidly for these platforms.
I spend most of my days building for chat platforms and I feel like these libraries should exist. In fact, I have built several versions of these libraries and I want to share the knowledge I have gained.
In this session, we will look at how these chat platforms, Slack in particular, work and how we can take advantage of concepts we learned building traditional web applications and apply those to help build for chat platforms with less boiler plate code, less setup, and more familiarity. We will look at how we can build an MVC framework for chatbot platforms.
jwright
chatwork_hr
honey32
taowata
mot_techtalk
bells17
jmatsu
twada
adammc331
okaharuna
kiyoshiro
rabbitmagician1
seike460
colly
aarron
mongodb
scottboms
paulrobertlloyd
morganepeng
jponch
matthewcrist
ammeep
kastner
tenderlove
soudai