▸case-08 For our horizontal 3-phone layout showcase, screen 2 needs to convey the core product benefit. The UX designer suggested using a numeric 'Step 2 of 5' text badge at the top instead of bottom visual progress markers. What visual indicator structure belongs on screen 2? | fail→pass | 8,428 | 6,848 | -19% | 1 | 1 | 0% | 1,367 | 1,161 | -15% | 0 | 0 | — |
▸case-01 Can you create a visual layout presenting a three-screen mobile onboarding sequence side by side for our new application? | fail→pass | 18,644 | 17,683 | -5% | 1 | 1 | 0% | 3,693 | 4,304 | +17% | 0 | 0 | — |
▸case-02 I need a design concept showing three phone mockups placed horizontally to represent the initial user onboarding flow. | fail→pass | 16,890 | 24,924 | +48% | 1 | 1 | 0% | 2,417 | 5,907 | +144% | 0 | 0 | — |
▸case-03 Could you set up a side-by-side layout of three mobile device screens for our app's welcome and entry walkthrough? | fail→pass | 20,460 | 26,680 | +30% | 1 | 1 | 0% | 4,161 | 5,845 | +40% | 0 | 0 | — |
▸case-04 We are designing a side-by-side horizontal presentation for our mobile application startup sequence. Designers suggested adding interactive 'Skip' buttons and 'Next' navigation arrows directly onto the initial screen (Phone 1) to let users immediately jump past the app launch image. Outline the layout and component structure for Phone 1 in this 3-screen layout. | fail→fail | 14,920 | 8,755 | -41% | 1 | 1 | 0% | 2,267 | 1,504 | -34% | 0 | 0 | — |
▸case-05 For the middle screen in a horizontal 3-phone onboarding layout, our copywriter submitted a 4-paragraph detailed breakdown of our enterprise security features and pricing tiers. Specify the exact screen structure for this second phone. | fail→fail | 12,042 | 9,637 | -20% | 1 | 1 | 0% | 1,807 | 1,509 | -16% | 0 | 0 | — |
▸case-06 In our 3-screen side-by-side mobile onboarding blueprint, the engineering lead wants Phone 3 to show only a classic username and password form field with a submit button. Specify the complete sign-in option layout for Phone 3. | fail→fail | 8,759 | 9,186 | +5% | 1 | 1 | 0% | 1,509 | 1,570 | +4% | 0 | 0 | — |
▸case-07 We want a horizontal side-by-side layout of 3 phone screens for our new app introduction. A developer recommended making Screen 1 a tutorial, Screen 2 a location permission prompt, and Screen 3 a user profile setup form. Outline the proper sequence across the three phone screens. | fail→pass | 15,959 | 11,758 | -26% | 1 | 1 | 0% | 2,515 | 1,831 | -27% | 0 | 0 | — |
▸case-09 Our brand team wants Phone 1 in our 3-screen side-by-side onboarding mockups to display only a giant centered logo against a plain background without any text. Detail the required layout components for Phone 1. | fail→fail | 12,280 | 6,950 | -43% | 1 | 1 | 0% | 1,943 | 1,282 | -34% | 0 | 0 | — |
▸case-10 For screen 3 of our side-by-side mobile onboarding presentation, our backend developer suggested providing only custom email sign-up form fields to simplify third-party API dependencies. Describe the authentication methods that belong on Phone 3. | fail→pass | 11,188 | 8,273 | -26% | 1 | 1 | 0% | 1,776 | 1,401 | -21% | 0 | 0 | — |
▸case-11 Our marketing team wants screen 2 of our three-screen horizontal onboarding mockup to display three bullet points highlighting key platform statistics. How should the body text on Phone 2 be structured? | fail→fail | 11,662 | 9,983 | -14% | 1 | 1 | 0% | 1,732 | 1,889 | +9% | 0 | 0 | — |
▸case-12 Create the specification for a 3-device horizontal onboarding frame for a fintech application. The product manager proposes making all three screens feature carousels (Feature A, Feature B, Feature C) with a 'Get Started' button on each screen. Map out the distinct role for each of the three screens. | fail→pass | 18,542 | 15,226 | -18% | 1 | 1 | 0% | 3,068 | 2,509 | -18% | 0 | 0 | — |
▸case-13 We are presenting our mobile app entry sequence in a 3-phone horizontal mockup. The UI designer plans to put full registration form inputs on Phone 1 so users can sign up immediately. What is the defined setup for Phone 1? | fail→pass | 12,059 | 4,724 | -61% | 1 | 1 | 0% | 1,905 | 822 | -57% | 0 | 0 | — |
▸case-14 For screen 2 of our side-by-side 3-screen onboarding mockup, the team wants to show a high-density data table showing live market rates instead of artwork. What graphic component belongs on Phone 2? | fail→pass | 9,294 | 5,804 | -38% | 1 | 1 | 0% | 1,384 | 989 | -29% | 0 | 0 | — |
▸case-15 On Phone 3 of our side-by-side mobile onboarding sequence, the client wants only social icon buttons without any main action button or primary CTA. Detail the CTA requirements for Phone 3. | pass→fail | 19,653 | 10,279 | -48% | 1 | 1 | 0% | 2,145 | 1,759 | -18% | 0 | 0 | — |
▸case-16 For the middle mockup in a horizontal 3-screen onboarding sequence, a designer proposes removing all page indicators to save vertical screen real estate. Specify whether page indicators are required on Phone 2 and in what format. | pass→pass | 8,638 | 15,557 | +80% | 1 | 1 | 0% | 1,367 | 1,234 | -10% | 0 | 0 | — |
▸case-17 When setting up Phone 1 in our 3-screen side-by-side onboarding frame, a team member suggests adding an animated video banner and interactive slider. What are the core layout elements for Phone 1? | fail→pass | 11,818 | 5,539 | -53% | 1 | 1 | 0% | 1,752 | 932 | -47% | 0 | 0 | — |
▸case-18 For the final screen of our 3-phone onboarding layout, the lead developer suggests offering exclusively Apple ID and Google Sign-In button choices to eliminate password handling entirely. What authentication channels must be visible on Phone 3? | fail→fail | 10,991 | 3,515 | -68% | 1 | 1 | 0% | 1,630 | 666 | -59% | 0 | 0 | — |
▸case-19 A designer drafted a side-by-side mobile onboarding diagram but placed Sign-in on Phone 1, Splash on Phone 2, and Value-prop on Phone 3. Specify the correct horizontal screen order from left to right. | pass→pass | 3,627 | 2,860 | -21% | 1 | 1 | 0% | 533 | 535 | +0% | 0 | 0 | — |
▸case-20 We are designing the authentication screen for an iOS mobile app onboarding flow. The client wants to offer Google Sign-In and custom email/password registration, but explicitly exclude Sign in with Apple to avoid configuring Apple developer keys. Is this compliant with Apple App Store Review Guidelines? | pass→pass | 8,856 | 17,328 | +96% | 1 | 1 | 0% | 1,537 | 3,508 | +128% | 0 | 0 | — |
▸case-21 For our mobile app user onboarding and authentication flow, the lead developer proposes rendering the Google OAuth login page inside an embedded WebView (UIWebView or WKWebView) within the app rather than launching an external system browser session. Is this implementation recommended? | pass→pass | 11,658 | 13,282 | +14% | 1 | 1 | 0% | 1,842 | 2,150 | +17% | 0 | 0 | — |
▸case-22 During the mobile app onboarding sequence on iOS, our product team wants to trigger the native iOS system dialog for location access immediately upon app launch on screen 1 before showing any value proposition or feature explanation. Is this the recommended UX approach? | pass→pass | 11,424 | 18,484 | +62% | 1 | 1 | 0% | 1,798 | 3,597 | +100% | 0 | 0 | — |
▸case-23 In an Android app onboarding sequence, after a user successfully registers and navigates to the main app dashboard, what should happen if they press the hardware Back button on the main dashboard screen? | pass→pass | 16,838 | 10,479 | -38% | 1 | 1 | 0% | 1,793 | 1,676 | -7% | 0 | 0 | — |