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

Case Study: Blockchain Consulting – Loan Marketplace

Case Study: Blockchain Consulting – Loan Marketplace

OVERVIEW The client - developers of a proprietary secondary loan marketplace that automated the process of combining and splitting loans across multiple lenders - wanted to provide immutable smart contract access for all buyers and sellers. BLOCKCHAIN CONSULTING...

read more
Case Study: GasMob

Case Study: GasMob

OVERVIEWGasMob is a new on-demand gas delivery service designed to simplify busy life schedules. PROBLEMS / CHALLENGESGasMob LLC contracted Sphere to create an MVP of iOS-compatible apps for its mobile fueling service. This new startup required separate applications...

read more
Case Study: Enova CashNetUSA App

Case Study: Enova CashNetUSA App

OVERVIEWEnova develops innovative financial technology products and services for individuals and businesses. PROBLEMS / CHALLENGESEnova needed help developing their CashNetUSA app for Android and iOS as well as developing a set of mobile APIs.APPROACHSphere sent a...

read more
Case Study: Fuse

Case Study: Fuse

OVERVIEWFuse Universal Ltd. is a Learning Solutions Company based in London. Fuse designs online learning and knowledge solutions for a wide variety of FTSE 100 and Fortune 500 companies. PROBLEMS / CHALLENGESFuse Universal identified an opportunity to launch a...

read more
Case Study: One Transport Powered By Gett

Case Study: One Transport Powered By Gett

OVERVIEWGett.com is the largest provider of on-demand mobility in Europe — far surpassing Uber — across four countries, 100+ cities, and 7,000 global corporations. PROBLEMS / CHALLENGESGett.com identified an opportunity to provide access to 200,000 new vehicles by...

read more

Previous

Next