The client needed help building mobile products on an accelerated timeframe

OVERVIEW

Sphere was asked to build a mobile application that allows employees to pay for a taxi using a corporate account.  The goal was to build a MVP within 3 months that shares 90%+ or more of the code between iOS and Android as well as important structural commonalities between mobile and web versions

TEAM

For the MVP, the Sphere team included three developers, one designer, and two shared QA analysts.  

APPROACH

The client’s requirements were quite fluid. Features were added and subtracted with each sprint. However, the basic flow of the project followed an agile test/release process.

  1. Business requirements received
  2. Designer creates mock-ups
  3. Mock-ups discussed and reviewed and revised internally
  4. Client approves designs or another round of adjustments takes place
  5. Development
  6. QA
  7. Wash, rinse, repeat

Within that deadline, bi-weekly sprints kept the team on a rapid release schedule. The team used Slack and Jira with bi-weekly sprints. In person and video meetings occurred on a regular basis to keep the team connected.

TECHNOLOGIES USED

For fast prototype creation against an accelerated timeline and to preserve a common code-base across iOS, Android, and web, React Native was used for Android, and iOS while Ruby on Rails was used for the backend. In addition, other tools used included:

  • Jira
  • Zeplin
  • GitHub
  • Overflow
  • Codeclimate
  • Airbrake

Deciding on a tech stack for this project was not easy since requirements were flexible and the end state was not well documented. The team recognized that the limitations of standard mobile development approaches (Swift – iOS, Java – Android) would not work given the constraints of budget and timeframe.

A cross-platform approach was required. With React native and React.js using JavaScript under the hood, mobile developers were able to reverse-engineer the existing web app to better understand the feature logic and how it should work. React Native was selected because it allowed a single codebase and reuse for multiple platforms – making it less expensive to create and maintain apps for iOS and Android.

OUTCOME

A  MVP was completed within the three-month deadline.  The MVP was released for internal use. Testing followed, and then after acceptance testing, the app was made available publicly.   So far, the app is responsible for 20% of all orders on the platform. This number is growing every week.

Understand the trade-offs of technical debt

How do you strike the right balance between feature development and the handling of technical debt? New white paper now available.

Talk to the team that worked on this project

Related Case Studies & Resources

Unleashing Agile Development to Improve Education

Unleashing Agile Development to Improve Education

  Fernando DeLeon is Co-Founder and Chief Product Officer of Innovare, a software solution seeking to improve the quality of education across the U.S. and Mexico.  During a recent Chicago TechDebate, Fernando talked about his technology product...

read more
Making Agile Development More Comfortable

Making Agile Development More Comfortable

  Belinda Hardman is a senior project manager/Scrum master for Morningstar. She shared her wealth of project management expertise within the technology sector during a recent TechDebate in Chicago in which the panel discussed the applications...

read more
Implementing Agile in Unexpected Places

Implementing Agile in Unexpected Places

  At a recent TechDebate in Chicago, we discussed implementing agile and apply agile to traditionally non-agile scenarios. We had a lively exchange, and fortunately, I had the chance to discuss the topic further with one of the panelists,...

read more
High-Performance Computing Use Cases

High-Performance Computing Use Cases

  Understanding High-Performance Computing Use Cases Some background Cloud computing as a business is fairly new. It was introduced by Amazon in 2006, followed by Google beta product in 2008, and last but not least - Microsoft released its...

read more
Agile planning – building an agile organization

Agile planning – building an agile organization

  Agile Planning - Creating and Reaping the Benefits of an Agile Organization The legendary boxer Mike Tyson once said, "Everybody has a plan until they get punched in the mouth." While Tyson has plenty of areas of personal weakness, his...

read more

Previous

Next