Problem: Authorization screens are a common reason for App Store rejection. If you add Google sign-in but forget the Apple ID button, expect a rejection. We design auth forms that pass moderation on the first try. With 5+ years of experience, we guarantee compliance with platform requirements. Inline validation boosts conversion by 30% compared to popup errors, and biometrics cuts login time by 40%. Moreover, according to our data, 80% of users abandon registration due to form complexity — we reduce that churn to 15%.
How to design authorization screens according to guidelines?
We start by analyzing the requirements of the App Store and Google Play. On iOS, we always implement Sign in with Apple (App Store Review Guidelines § 4.8). On Android, we ensure that BiometricPrompt is not customized and uses the system dialog. The designer must anticipate all states: loading, error, empty, success. The number of states can reach 10 — from successful login to account lockout. Using inline validation reduces erroneous submissions by 3 times compared to popups.
What screens are included in the set?
- Login — email/phone + password, social network buttons (order: Apple first on iOS, then Google, Facebook). Inline validation under fields, no popups. Spinner inside the button on submission (not just disabled).
- Register — minimal set. Collect only email and password initially; birth date or phone later in the profile.
- Forgot Password — one email field, confirmation screen with instructions (check spam, retry timer).
- Biometrics — Face ID / Touch ID / Android BiometricPrompt. The login button shows a badge if biometrics is enabled.
Why is the order of social login buttons important?
On iOS, Apple requires that Sign in with Apple appears above other providers. This is not just a recommendation — without it, the build may be rejected. On Android, the order is not regulated, but UX best practices suggest placing Google first. We always verify compliance with App Store Review Guidelines and Google Play Policy.
Technical details affecting design
Does the keyboard cover the fields? On iOS, we use UIScrollView with contentInsetAdjustmentBehavior to scroll under the keyboard. The designer must specify: does the form scroll or shift up? The Submit button should not hide under the keyboard. Password field — secureTextEntry with a show/hide icon on the right. Autofill — set textContentType (iOS) and autofillHints (Android). Floating labels — lift on focus. Development time savings from ready-made components can reach 30%.
| Aspect | iOS | Android |
|---|---|---|
| Biometrics | LAContext / LocalAuthentication | BiometricPrompt (system) |
| Social login | Sign in with Apple required | Google Sign-In, not required |
| Autofill | textContentType | autofillHints |
| Push notifications | APNs (register via UIApplication) | FCM (service) |
| Deep linking | Universal Links | App Links |
Main states of the authorization screen
| State | Description | Visualization |
|---|---|---|
| Loading | Spinner in button, fields disabled | Semi-transparent overlay or skeleton |
| Error inline | Message under field (red text) | Field border highlight |
| Success | Transition to main screen | Checkmark animation, then transition |
| Offline | Banner at top "No connection" | Yellow banner with icon |
How we design: process from idea to deployment
- Analysis — study App Store / Google Play requirements, determine the minimum set of screens. Recognize that 80% of users abandon registration due to complexity.
- Design — create User Flow (login → home, register → email verification → home). Work out error states and loading.
- Prototyping — Figma with components: buttons, fields, modals. Connect Zeplin for developer handoff.
- Implementation — iOS (Swift 5.9, SwiftUI), Android (Kotlin, Jetpack Compose), or Flutter 3.x. Adhere to App Store Review Guidelines.
- Testing — verify all states, including offline and orientation change.
- Deployment — TestFlight / Firebase App Distribution. Attach screenshots with Apple ID buttons.
Typical mistakes we avoid:
- Missing Apple ID button on iOS
- Custom biometric dialog instead of system
- Popup validation instead of inline
- Disabled buttons without spinner
- Collecting unnecessary data during registration
What is included in the work
- UX flow diagram of all auth states
- Figma mockups (login, register, forgot, success/error, loading)
- Export assets (SVG, PNG) in three sizes
- Developer documentation — specification of states and animations
- Support during moderation (up to 2 rejections)
- Access to a repository of UI components (SwiftUI / Compose)
Timeline
Complete set of screens (login, register, forgot, biometrics, all states) — from 1 to 3 working days depending on animation complexity. We will estimate the project for free after receiving a brief.
Why choose us
We design auth forms that pass App Store and Google Play reviews without extra iterations. Our experience: 5+ years and 30+ projects in mobile development. We guarantee compliance with guidelines and compatibility with the latest iOS and Android versions. Order turnkey design of authentication screens — write to us in Telegram or email. Get a consultation on your app's UI/UX. Contact us to start the project.