ZIING MOBILE APPLICATION

THE DIFFERENTIATOR

In an effort to revolutionize community engagement, Ziing is focused on connecting people to social activities organically, cutting through the noise experienced in most typical social media platforms by parsing the message of an event down to the “when” and “where” of what people are actually looking for in their fragmented social feeds.

Ziing intends to foster a unique social dynamic and experience for everyone by making it easier for people to connect with those who share an interest in an event who are close enough to care about it and who most likely want to participate in it based on their interests.

THE EXECUTION

With a strong concept and design in place from the founders and designers, Ziing needed to start to build their application and hired AccelOne who:

• Architected and built both the native iOS and Android mobile applications
• Built the back-end layer in MongoDB and Nodejs in AWS
• Used Scrum and Agile methodologies

AccelOne broke this project down into two phases and Sprints, each with three iterations:

1. design phase
2. development phase
3. user acceptance testing (UAT)

To accomplish this workload, the work was split into seven (7) sprints, each encompassing three (3) weeks of work. After each sprint, a new deliverable was shared.

The team configuration consisted of six resources: four (4) senior-level developers, including two (2) Senior iOS Developers, a Senior Android Developer, and a Back End Senior Developer, a Mobile QA Analyst, and the Product Owner, who oversaw production and gave precise specifications.

Throughout the project, the Scrum Master and Product Owner consulted and collaborated in order to decide which user stories would be implemented across the different iterations of the project. As a result, essential project parameters were set in place, including weekly meetings and a near-constant level of communication between all members of the team.

With the team in place, AccelOne’s team exposed all of the software parameters for each of the devices in order to understand their nuances. Two back end server environments were put in place: Staging, for preview/QA Beta versions, and Production, to serve release versions of the application.

The first phase of the application, encompassing about three (3) months of work, included the completion of the architecture of the iOS Application and Back-end. Also completed in this time were the login process and initial framework for Ziing support.

Once the initial phase was delivered, tested, and accepted, the second phase of the project was initiated. This phase involved a callback to previous work done in the iOS Application and Back-end. We began finalizing functionality for each, while adding the required remaining functionality to complete the product, plus an Android native version of the application. We found we would require the UUIDs of the different devices where the application would be installed in order for internal testing.

The technology stack was as follows:

• iOS Application was created using Native Objective C/Swift 2 application while Android was created using Native Java application.
• Back-end was made via Nodejs exposing endpoints in a full rest API. As for the frameworks for specific tasks, Passportjs was utilized for authentication while Mongoosejs was used for object modeling.
• Additionally, MongoDB was used for storing events, contacts and other documents required by the application.