Written by Qudini’s Mobile Development Team
Last week, Qudini tech mobile team went to Mobile@Scale event at Facebook London office, focusing on the best way to scale mobile apps. During this event, some of the best practices explained are already implemented within our solutions. Here are some of the best practises we use at Qudini to get the best scalable app.
One of the talks during Mobile@Scale focused on how Spotify manages their backend to drive UI mobile, and how they can update their UI / UX mobile app depending of their api. It’s something we have done at Qudini to tailor the apps UI depending on client needs.
Based on the same idea, Qudini Retail app (shown above) will adapt the UI depending on the clients branded colours and logo, but also customise the communications sent through our queue management app solutions (Retail App or Click & Collect). Our mobile apps can also handle user’s permissions like concierge or advisor roles, helping our clients best manage their staff (assigning available staff to waiting customers) and improve the quality of service each customer receives.
Finally, as the popularity of Self Service Kiosk increases, Qudini’s Kiosks will allow clients to design their own kiosk app to fit to their requirements, to ensure customer facing solutions provide a brand constancy at every touchpoint. Our Self Service kiosks also allow customers to switch between multiple languages, catering for the international market.
One of the key points to get a scalable app, is reducing the delivery time, and for iOS, it can be done by reducing submissions on the App Store. At Qudini, we manage this by using feature flags.
Our cycle release is around 6 to 8 weeks. When a feature is ready to go onboard next release train, we leave a feature flag within the app that we can remotely switch on and off a new feature, ensuring that there is a control on how the new feature is tested by our clients. This feature is easy to manage with controls set within the backend side of our application.
As our queuing management system solution is also based on the specific needs of each client, we use the same process to enable dedicated feature to them.
Feature flags are invisible to the final user, and allow for new queuing features to be released without updating clients having to update all devices across their stores.
What’s Next for Qudini
At Mobile@Scale, there were great talks on cross platform solution, such as React Native technology from Facebook, or how to manage mobile development by installing pair programming or feature team (and mixing developer, designer and product developer skills) instead of a full mobile team.
All these solutions have given us lots of ideas to develop on, so we can keep improving our mobile solutions and distributing the best experience to our end users…..Technology and development never stops moving, and the same can be applied to the education and technical developments within Qudini.