+1 -1 -2
Vote on this proposal

When SMS/USSD feeds data to WebApp.

by Pooja Salpekar (speaking)

Section
Web Development
Technical level
Intermediate

Objective

Developing a Web App can become trickier when you have data coming in via SMS or USSD inputs. Also, with development, testing becomes more challenging.
This talk covers challenges and learnings from past experiences.

Description

For most of us who have been involved in web development/desiging, would know that even though they say- "Its just a web app, how hard it can be?", it's never that simple. Every web development has got its own hitches. Yes, we always manage to solve them, and not to forget- the learnings.

On similar note, some of my learnings while working on sms-based and USSD-based web apps.
When your development is based on inputs from these data sources, testing your application and more importantly automating these tests becomes challenging.

Writing an applications that sends and handles USSD responses, was truely one of my proud learnings. Specially now-a-days when all kind of jazz is done in your smart phones, getting a chance to deal with pains and perks USSD is worth mentioning.

Session will include:
- A quick demo app integrating responses from USSD/SMS. - Testing strategies to cover end to end tests for these kind of applications.

Speaker bio

Pooja Salpekar is an Application Developer at ThoughtWorks. Pooja has been developing software in Ruby on Rails and Python-Django based web-apps throughout her career. She has worked on SMS integrated web apps and USSD based projects in Africa, drove the development of Test Trend Analyzer (a ThoughtWorks product) and was part of the team that worked on load balancing on Cloud Computing environment.

She enjoys mentoring, and has conducted ruby sessions for college students in Uganda, teaching them the basics of Ruby based Web-Development. Passionate about writing clean code, Pooja has a penchant for exploring anything new, be it frameworks, development paradigms, technical or non-technical.

Comments

Login with Twitter or Google to leave a comment →