The problem.
Cialfo helps students find universities, keep a shortlist, apply and talk to their counsellor. I worked on the React Native app as part of the product team.
A student’s search, saved choices, applications, tasks and messages live on different screens. New features had to keep all of that in sync and go out through the team’s normal release process.
How I approached it.
Knowing the app’s parts
The app is split into areas: university search, lists, direct apply, inbox, meetings and tasks. Knowing where each feature belonged made changes safer.
App data and server calls
The app uses Redux, Redux Saga and Axios. I worked on how student data and server calls are handled in the screens I built. I didn’t write the whole data layer.
Working with product and design
I built features, worked on application tracking, worked closely with product and design, and helped with releases.
What I built.
- React Native features for students
- Application tracking screens
- App data and server-call handling
- Help with mobile releases
I shipped React Native features and application-tracking screens with the Cialfo team, and helped with releases.
Mobile work by Talha at Cialfo. The product belongs to Cialfo.
What I learned.
When one app covers many areas, keeping each area’s data separate makes new features much easier to add.
If you have a mobile SaaS app, I can build new features, review how the app handles its data, and work with your product and design team.