RindID | Tulon

RingID

Overview

I worked at RingID for over 3 years as part of a team of 40+ iOS developers. RingID is a social media app known for features like call, chat, feed, friends, and live streaming, with a user base of over 1 million. Initially serving as a product manager, I later transitioned to the Authentication team. This team was responsible for implementing comprehensive social media sign-up and sign-in functionalities, as well as enabling users to register and log in through email and mobile phone (Fabric). Subsequently, I contributed to the overall UI and the Settings panel of the project.

Role and Responsibilities

As a product manager, my responsibilities included researching existing apps such as Facebook, Instagram, Tango, Whatsapp, IMO, which are similar to RingID. After conducting the research, I discussed my findings with the CEO and CTO. If the features aligned with the business model, I would then hand them over to the development team for implementation. I collaborated with the development team on aspects like architecture, Data Model, and UI/UX.

Within the Authentication team, I led the implementation of social media authentication for Google, Facebook, Twitter, covering both UI and functionalities. I also played a crucial role in enabling users to register and log in through email and mobile phone (Fabric).

The entire project's UI/UX was under my responsibility for all modules, and I was accountable for both the UI and functionality development of the Settings panel for the entire project.

Project Duration

From February 2015 to October 2018.

Challenges and Solutions

This app was developed for Android, Windows Phone, and the web, presenting the challenge of ensuring consistency across all platforms despite their inherent differences. The frequent changes in UI/UX made it a bit challenging to maintain a clean code base and architecture while still achieving our goals.

The utilization of the UDP protocol in the project posed unique data handling challenges. The absence of guaranteed delivery and packet order necessitated the implementation of robust error-handling mechanisms. Furthermore, to ensure seamless communication, we encountered instances where modifications to the main parser were necessary.