Big up to 7cups.com
Trigger.io users are people we are proud to be associated with! The recent growth of 7cups.com is a testament to the kind of skill and effort we regularly encounter amongst the Trigger.io community.
The aim of the 7cups initiative is to provide online emotional support in a world with “an immense love deficit”. From their website:
7 Cups of Tea is an on-demand emotional health and well-being service. Our bridging technology anonymously & securely connects real people to real listeners in one-on-one chat.
Anyone who wants to talk about whatever is on their mind can quickly reach out to a trained, compassionate listener through our network. We have hundreds of listeners who come from all walks of life and have diverse experiences.
Glen Moriarty, Founder and CEO, is a psychologist who is passionate about the Internet’s power to help people lead better lives. He is joined by a team of professionals with a wide range of capabilities, from counselling and social work to engineering and web design.
As well as a running a succesful website and an app which is available on both IOS and Android, 7cups also maintains an active reddit community, and encourages academic research interest through their Open Research Platform
Working with Trigger.io
We asked Ezra Morse, the Full Stack Engineer at 7 Cups, to tell us a little about working with Trigger.io as a platform for development.
Q – Why did 7cups choose to work with Trigger.io?
As the world’s largest emotional support network, 7 Cups is about bringing people together. The last thing we need is to sacrifice dev time on hunting for platform bugs, solving plug-in conflicts and triaging build issues.
Trigger.io allowed us to swiftly convert a legacy, first-generation mobile website into a reactive one-page application with the native plug-ins we needed, while keeping our focus where it should be: on user experience and our community.
In the end, we were able to produce a lean, performant app that isn’t mired by stability issues or the long iterative cycles characteristic of a fully native app. We finally have a stable and evolving application that better positions us to reach more people in need.
Q – What is your overall experience of hybrid development in today’s market?
To be honest, Trigger.io wasn’t our first choice on this project. Let’s just say that our first pass at modernizing our app could be described as wanting to have our cake and eat it too.
We bought into too many promises and tried to relegate far too much functionality (UX included) to the native device, thereby leaving us with a slow, bloated hybrid-application that would crash as often as freeze. So we went from an extremely bad scenario where our concerns about speed and the memory footprint of the app simply didn’t allow us to take any chances.
If we wanted to keep our app hybrid, a cordova-flavor just wasn’t going to give us the lean and stable app we wanted to share with the world; we simply could not afford to have performance issues continue to stand in between the people on each end of the device.
In summary, I feel a lot of the hybrid approaches fail to keep it simple on both the application level and the build process, and thereby, the end product suffers. As hybrid developers, should we really need to focus on too much more than what is going on inside that single webview?
Thanks Ezra, for making the time to speak to us and fill us in on your development process. We look forward to many more collaborations in the coming months.
From everyone at Trigger.io, keep up the good work!