Login & Signup Result Improvement in Swiggy Android App
Article Summary
Swiggy was losing users during login and signup despite optimizing app size and launch time. The culprit? Manual data entry errors.
Viswanathan K P from Swiggy's mobile team shares how they leveraged Android's Autofill Framework and Phone Selector API to reduce friction in their authentication flow. This is part of Swiggy's broader mobile optimization efforts following their app size and cold start improvements.
Key Takeaways
- 25% more users completed signup successfully with autofill for name, email, and phone
- 4% more users reached OTP screen using Phone Selector hint API
- Autofill Framework requires Android 8.0+ and proper hint implementation
- Phone Selector API needs no permissions and returns E.164 formatted numbers
- Mark fields with importantForAutofill to control what gets autofilled
By implementing Android's Autofill Framework and Phone Selector, Swiggy reduced authentication friction and improved signup completion by 25%.
About This Article
During login and signup, users often made mistakes entering phone numbers and emails, which led to form submission failures and people abandoning the process on Swiggy.
Viswanathan K P's team added Android's Autofill Framework (API 26+) with autofillHints attributes and the Phone Selector API. This let the app fill in user information automatically instead of requiring manual entry.
Signup completion went up by 25% when autofill populated name, email, and mobile number. Login conversions to the OTP screen also increased by 4% using the Phone Selector hint feature.