Preview the prompt +
# Build brief — an original mobile app in the taste of MobilEM
> Reference: https://apps.apple.com/us/app/mobilem/id1474834329 · UIDiscovery: https://uidiscovery.com/sites/ios-mobilem · captured 2026-09-22
## 1. Goal
Build an original mobile app for **[the user's brand]** that feels as considered as MobilEM — same structure, rhythm and polish, entirely new identity and content. Stack: SwiftUI, React Native/Expo, or a mobile-first web app.
## 2. Originality rules
- Build an ORIGINAL design for the user's own brand in the same *taste* as MobilEM: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse MobilEM's logo, name, product imagery, illustrations, icons, screenshots or copy. Write new copy for the user's product.
- If the user hasn't said what their product is, ask first (or use clearly marked placeholders like [Brand], [Product], [Audience]).
- Reference screenshots are for looking at, not for embedding or tracing.
## 3. The taste, in short
- MobilEM is a Medical iOS app rated 3.6 on the App Store; 6 screens captured.
- Screens are App Store listing images (marketing frames around real UI) — read layout from the phone area, ignore the marketing captions.
- Palette and fonts are NOT measured for iOS references — sample them from the screenshots.
## 4. Screens
Every screen needs: Status bar + navigation; Primary content; Primary action / tab bar; Empty and loading states.
1. [Screen](https://uidiscovery.com/media/captures/ios-mobilem/screen-01.jpg)
2. [Screen](https://uidiscovery.com/media/captures/ios-mobilem/screen-02.jpg)
3. [Screen](https://uidiscovery.com/media/captures/ios-mobilem/screen-03.jpg)
4. [Screen](https://uidiscovery.com/media/captures/ios-mobilem/screen-04.jpg)
5. [Screen](https://uidiscovery.com/media/captures/ios-mobilem/screen-05.jpg)
6. [Screen](https://uidiscovery.com/media/captures/ios-mobilem/screen-06.jpg)
## 5. Design system
- Colour: not measured. The listing hints at `#f8f8f8` (probably from the icon) — a hint only. Sample background, text, accent and surface from the screenshots, then check contrast.
- Type: SF Pro natively (Dynamic Type: Large Title 34, Title 22–28, Body 17, Footnote 13); on the web use Inter or system-ui at the same sizes.
- Layout: 16–20pt side margins, 44pt minimum tap targets, safe areas, tab bar or navigation stack as seen in the screens; cards with 12–20pt radii are typical — confirm in the screenshots.
## 6. Imagery plan
iOS references show the product UI itself: build screens in code. What you still need to source is the content imagery inside them (covers, thumbnails, onboarding art).
### Slot 1 · All 6 screens → product UI
- iOS screen: the visual is the app UI itself; any photos/illustrations inside it are content. Count: one consistent treatment across these sections. Aspect: 9:16 (portrait, phone). Look first: [ref 1](https://uidiscovery.com/media/captures/ios-mobilem/screen-01.jpg) [ref 2](https://uidiscovery.com/media/captures/ios-mobilem/screen-02.jpg) [ref 3](https://uidiscovery.com/media/captures/ios-mobilem/screen-03.jpg) [ref 4](https://uidiscovery.com/media/captures/ios-mobilem/screen-04.jpg)
- Build every screen in code. Don't reproduce App Store marketing frames or the app's own artwork.
### Slot 2 · In-app content imagery (covers, thumbnails, onboarding art) → photography (uncertain)
- Medical apps often use photography for content — not measured; check the screenshots. Count: one consistent style across all content. Aspect: 1:1 thumbnails, 4:5 covers. Look first: [ref 1](https://uidiscovery.com/media/captures/ios-mobilem/screen-01.jpg) [ref 2](https://uidiscovery.com/media/captures/ios-mobilem/screen-02.jpg) [ref 3](https://uidiscovery.com/media/captures/ios-mobilem/screen-03.jpg)
- **Stock** — “doctor talking with patient”: [Unsplash](https://unsplash.com/s/photos/doctor-talking-with-patient?orientation=landscape) · [Pexels](https://www.pexels.com/search/doctor%20talking%20with%20patient/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/doctor%20talking%20with%20patient/?orientation=horizontal)
- **Generate** — `Photograph: doctor talking with patient. Composition: centred subject with even space around it. Lighting: soft natural daylight, airy and high-key. Neutral, desaturated colour grade that sits on colours sampled from the reference screenshots (the listing hints at #f8f8f8). Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 16:10. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`
- **Licences:** Unsplash and Pexels images are free for commercial use under their own licences; Pixabay under the Pixabay Content License. Check each image's page before use, credit the photographer when asked (good practice anyway), and skip images showing logos, trademarks, branded products or identifiable people without a release.
- **AI generation:** the prompts work with any image model (GPT Image, Imagen, Flux, Midjourney, Firefly, SDXL…) — check its commercial-use terms. Never put the reference brand's name or “in the style of <brand>” in a prompt.
- **Never** download, trace or re-host the reference's own images, illustrations, product shots or logos.
## 7. Build steps
1. Confirm brand, product, audience and the primary action with the user.
2. Pick the stack and define colour/type tokens sampled from the screenshots.
3. Build the navigation shell first, then each screen, with each reference screenshot open.
4. Write original copy for every slot — match length and tone, never the words.
5. Source every image via the imagery plan (stock or generated); compress it and record credits.
6. Run the checklist at 390 / 768 / 1440px and fix what fails.
## 8. Acceptance checklist
- [ ] Responsive at 390px, 768px and 1440px — no horizontal scroll, tap targets ≥ 44px on mobile.
- [ ] Colour contrast WCAG AA: 4.5:1 body text, 3:1 large text and UI; visible focus states; full keyboard navigation.
- [ ] Semantic HTML: one <h1>, ordered headings, landmarks (header/nav/main/footer), labelled form fields, alt text on meaningful images.
- [ ] Performance: modern image formats with width/height set, lazy-load below the fold, ≤ 2 font families with font-display: swap, LCP < 2.5s.
- [ ] prefers-reduced-motion respected; animations under ~300ms and never blocking content.
- [ ] Originality: no copied logos, images, illustrations or copy from the reference; every image licensed or generated; credits recorded.
## 9. If you use Next.js + Tailwind
Mobile web: App Router + Tailwind, `viewport-fit=cover` with safe-area insets, a fixed bottom tab bar, components designed at 390px first.
---
More: tokens https://uidiscovery.com/api/v1/sites/ios-mobilem/tokens · kit https://uidiscovery.com/api/v1/sites/ios-mobilem/kit · MCP `get_design_brief({ slug: "ios-mobilem" })`, `get_image_plan({ slug: "ios-mobilem" })`. Cite the reference as https://uidiscovery.com/sites/ios-mobilem.
