Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases.
Assess Adaptation Challenge
Understand what needs adaptation and why:
Identify the source context:
- What was it designed for originally? (Desktop web? Mobile app?)
- What assumptions were made? (Large screen? Mouse input? Fast connection?)
- What works well in current context?
Understand target context:
- Device: Mobile, tablet, desktop, TV, watch, print?
- Input method: Touch, mouse, keyboard, voice, gamepad?
- Screen constraints: Size, resolution, orientation?
- Connection: Fast wifi, slow 3G, offline?
- Usage context: On-the-go vs desk, quick glance vs focused reading?
- User expectations: What do users expect on this platform?
Identify adaptation challenges:
- What won't fit? (Content, navigation, features)
- What won't work? (Hover states on touch, tiny touch targets)
- What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop)
CRITICAL: Adaptation is not just scaling - it's rethinking the experience for the new context.
Plan Adaptation Strategy
Create context-appropriate strategy:
Mobile Adaptation (Desktop → Mobile)
Layout Strategy:
- Single column instead of multi-column
- Vertical stacking instead of side-by-side
- Full-width components instead of fixed widths
- Bottom navigation instead of top/side navigation
Interaction Strategy:
- Touch targets 44x44px minimum (not hover-dependent)
- Swipe gestures where appropriate (lists, carousels)
- Bottom sheets instead of dropdowns
- Thumbs-first design (controls within thumb reach)
- Larger tap areas with more spacing
Content Strategy:
- Progressive disclosure (don't show everything at once)
- Prioritize primary content (secondary content in tabs/accordions)
- Shorter text (more concise)
- Larger text (16px minimum)
Navigation Strategy:
- Hamburger menu or bottom navigation
- Reduce navigation complexity
- Sticky headers for context
- Back button in navigation flow
Tablet Adaptation (Hybrid Approach)
Layout Strategy:
- Two-column layouts (not single or three-column)
- Side panels for secondary content
- Master-detail views (list + detail)
- Adaptive based on orientation (portrait vs landscape)
Interaction Strategy:
- Support both touch and pointer
- Touch targets 44x44px but allow denser layouts than phone
- Side navigation drawers
- Multi-column forms where appropriate
Desktop Adaptation (Mobile → Desktop)
Layout Strategy:
- Multi-column layouts (use horizontal space)
- Side navigation always visible
- Multiple information panels simultaneously
- Fixed widths with max-width constraints (don't stretch to 4K)
Interaction Strategy:
- Hover states for additional information
- Keyboard shortcuts
- Right-click context menus
- Drag and drop where helpful
- Multi-select with Shift/Cmd
Content Strategy:
- Show more information upfront (less progressive disclosure)
- Data tables with many columns
- Richer visualizations
- More detailed descriptions
Print Adaptation (Screen → Print)
Layout Strategy:
- Page breaks at logical points
- Remove navigation, footer, interactive elements
- Black and white (or limited color)
- Proper margins for binding
Content Strategy:
- Expand shortened content (show full URLs, hidden sections)
- Add page numbers, headers, footers
- Include metadata (print date, page title)
- Convert charts to print-friendly versions
Email Adaptation (Web → Email)
Layout Strategy:
- Narrow width (600px max)
- Single column only
- Inline CSS (no external stylesheets)
- Table-based layouts (for email client compatibility)
Interaction Strategy:
- Large, obvious CTAs (buttons not text links)
- No hover states (not reliable)
- Deep links to web app for complex interactions
Implement Adaptations
Apply changes systematically:
Responsive Breakpoints
Choose appropriate breakpoints:
- Mobile: 320px-767px
- Tablet: 768px-1023px
- Desktop: 1024px+
- Or content-driven breakpoints (where design breaks)
Layout Adaptation Techniques
- CSS Grid/Flexbox: Reflow layouts automatically
- Container Queries: Adapt based on container, not viewport
clamp(): Fluid sizing between min and max
- Media queries: Different styles for different contexts
- Display properties: Show/hide elements per context
Touch Adaptation
- Increase touch target sizes (44x44px minimum)
- Add more spacing between interactive elements
- Remove hover-dependent interactions
- Add touch feedback (ripples, highlights)
- Consider thumb zones (easier to reach bottom than top)
Content Adaptation
- Use
display: none sparingly (still downloads)
- Progressive enhancement (core content first, enhancements on larger screens)
- Lazy loading for off-screen content
- Responsive images (
srcset, picture element)
Navigation Adaptation
- Transform complex nav to hamburger/drawer on mobile
- Bottom nav bar for mobile apps
- Persistent side navigation on desktop
- Breadcrumbs on smaller screens for context
IMPORTANT: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect.
NEVER:
- Hide core functionality on mobile (if it matters, make it work)
- Assume desktop = powerful device (consider accessibility, older machines)
- Use different information architecture across contexts (confusing)
- Break user expectations for platform (mobile users expect mobile patterns)
- Forget landscape orientation on mobile/tablet
- Use generic breakpoints blindly (use content-driven breakpoints)
- Ignore touch on desktop (many desktop devices have touch)
Verify Adaptations
Test thoroughly across contexts:
- Real devices: Test on actual phones, tablets, desktops
- Different orientations: Portrait and landscape
- Different browsers: Safari, Chrome, Firefox, Edge
- Different OS: iOS, Android, Windows, macOS
- Different input methods: Touch, mouse, keyboard
- Edge cases: Very small screens (320px), very large screens (4K)
- Slow connections: Test on throttled network
Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly.
1---2name: adapt3description: Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases.4metadata:5 source: https://skillmd.com/skills/comeonoliver/adapt6---7Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases.89## Assess Adaptation Challenge1011Understand what needs adaptation and why:12131. **Identify the source context**:14 - What was it designed for originally? (Desktop web? Mobile app?)15 - What assumptions were made? (Large screen? Mouse input? Fast connection?)16 - What works well in current context?17182. **Understand target context**:19 - **Device**: Mobile, tablet, desktop, TV, watch, print?20 - **Input method**: Touch, mouse, keyboard, voice, gamepad?21 - **Screen constraints**: Size, resolution, orientation?22 - **Connection**: Fast wifi, slow 3G, offline?23 - **Usage context**: On-the-go vs desk, quick glance vs focused reading?24 - **User expectations**: What do users expect on this platform?25263. **Identify adaptation challenges**:27 - What won't fit? (Content, navigation, features)28 - What won't work? (Hover states on touch, tiny touch targets)29 - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop)3031**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context.3233## Plan Adaptation Strategy3435Create context-appropriate strategy:3637### Mobile Adaptation (Desktop → Mobile)3839**Layout Strategy**:40- Single column instead of multi-column41- Vertical stacking instead of side-by-side42- Full-width components instead of fixed widths43- Bottom navigation instead of top/side navigation4445**Interaction Strategy**:46- Touch targets 44x44px minimum (not hover-dependent)47- Swipe gestures where appropriate (lists, carousels)48- Bottom sheets instead of dropdowns49- Thumbs-first design (controls within thumb reach)50- Larger tap areas with more spacing5152**Content Strategy**:53- Progressive disclosure (don't show everything at once)54- Prioritize primary content (secondary content in tabs/accordions)55- Shorter text (more concise)56- Larger text (16px minimum)5758**Navigation Strategy**:59- Hamburger menu or bottom navigation60- Reduce navigation complexity61- Sticky headers for context62- Back button in navigation flow6364### Tablet Adaptation (Hybrid Approach)6566**Layout Strategy**:67- Two-column layouts (not single or three-column)68- Side panels for secondary content69- Master-detail views (list + detail)70- Adaptive based on orientation (portrait vs landscape)7172**Interaction Strategy**:73- Support both touch and pointer74- Touch targets 44x44px but allow denser layouts than phone75- Side navigation drawers76- Multi-column forms where appropriate7778### Desktop Adaptation (Mobile → Desktop)7980**Layout Strategy**:81- Multi-column layouts (use horizontal space)82- Side navigation always visible83- Multiple information panels simultaneously84- Fixed widths with max-width constraints (don't stretch to 4K)8586**Interaction Strategy**:87- Hover states for additional information88- Keyboard shortcuts89- Right-click context menus90- Drag and drop where helpful91- Multi-select with Shift/Cmd9293**Content Strategy**:94- Show more information upfront (less progressive disclosure)95- Data tables with many columns96- Richer visualizations97- More detailed descriptions9899### Print Adaptation (Screen → Print)100101**Layout Strategy**:102- Page breaks at logical points103- Remove navigation, footer, interactive elements104- Black and white (or limited color)105- Proper margins for binding106107**Content Strategy**:108- Expand shortened content (show full URLs, hidden sections)109- Add page numbers, headers, footers110- Include metadata (print date, page title)111- Convert charts to print-friendly versions112113### Email Adaptation (Web → Email)114115**Layout Strategy**:116- Narrow width (600px max)117- Single column only118- Inline CSS (no external stylesheets)119- Table-based layouts (for email client compatibility)120121**Interaction Strategy**:122- Large, obvious CTAs (buttons not text links)123- No hover states (not reliable)124- Deep links to web app for complex interactions125126## Implement Adaptations127128Apply changes systematically:129130### Responsive Breakpoints131132Choose appropriate breakpoints:133- Mobile: 320px-767px134- Tablet: 768px-1023px135- Desktop: 1024px+136- Or content-driven breakpoints (where design breaks)137138### Layout Adaptation Techniques139140- **CSS Grid/Flexbox**: Reflow layouts automatically141- **Container Queries**: Adapt based on container, not viewport142- **`clamp()`**: Fluid sizing between min and max143- **Media queries**: Different styles for different contexts144- **Display properties**: Show/hide elements per context145146### Touch Adaptation147148- Increase touch target sizes (44x44px minimum)149- Add more spacing between interactive elements150- Remove hover-dependent interactions151- Add touch feedback (ripples, highlights)152- Consider thumb zones (easier to reach bottom than top)153154### Content Adaptation155156- Use `display: none` sparingly (still downloads)157- Progressive enhancement (core content first, enhancements on larger screens)158- Lazy loading for off-screen content159- Responsive images (`srcset`, `picture` element)160161### Navigation Adaptation162163- Transform complex nav to hamburger/drawer on mobile164- Bottom nav bar for mobile apps165- Persistent side navigation on desktop166- Breadcrumbs on smaller screens for context167168**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect.169170**NEVER**:171- Hide core functionality on mobile (if it matters, make it work)172- Assume desktop = powerful device (consider accessibility, older machines)173- Use different information architecture across contexts (confusing)174- Break user expectations for platform (mobile users expect mobile patterns)175- Forget landscape orientation on mobile/tablet176- Use generic breakpoints blindly (use content-driven breakpoints)177- Ignore touch on desktop (many desktop devices have touch)178179## Verify Adaptations180181Test thoroughly across contexts:182183- **Real devices**: Test on actual phones, tablets, desktops184- **Different orientations**: Portrait and landscape185- **Different browsers**: Safari, Chrome, Firefox, Edge186- **Different OS**: iOS, Android, Windows, macOS187- **Different input methods**: Touch, mouse, keyboard188- **Edge cases**: Very small screens (320px), very large screens (4K)189- **Slow connections**: Test on throttled network190191Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly.