Mobile Web Domain Knowledge

Provide structured mobile and web domain knowledge for architecture planning.

Updated Feb 9, 2026

Search Tags:#architecture #performance #mobile #web #domain-knowledge #ux-patterns #platform-requirements

Ready to run

npx skills add https://github.com/Danhvb/my-ba-skills --skill mobile-web-domain-knowledge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Mobile Web Domain Knowledge
Source: https://github.com/Danhvb/my-ba-skills/tree/main/multi-agent-ba/.agent/skills/domain-knowledge/mobile-web
Command: npx skills add https://github.com/Danhvb/my-ba-skills --skill mobile-web-domain-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understand mobile and web domain knowledge to guide architecture decisions, UX patterns, performance, and platform-specific requirements.

Core Features & Use Cases

Comprehensive knowledge across mobile and web patterns (native, cross-platform, SPA/SSR/PWA)
Platform-specific considerations (iOS, Android, web) including accessibility, performance, and design guidelines
Use cases: planning architecture, evaluating trade-offs, and aligning stakeholders

Quick Start

Summarize best practices for mobile and web domain knowledge to guide architecture decisions.

Frequently Asked Questions about Mobile Web Domain Knowledge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What are the key architecture trade-offs between native, cross-platform, and PWA strategies?▼

Mobile and web architecture trade-offs differ by platform requirements. Native offers peak performance and full API access, cross-platform accelerates development, while progressive web apps maximize reach with responsive design and offline capabilities.

How do I decide between SPA and SSR for my web application architecture?▼

Choose SPA for highly interactive web interfaces with client-side routing, or SSR when prioritizing initial load performance and SEO. Evaluating these trade-offs requires mapping domain patterns against platform requirements and expected user experience.

What mobile and web UX patterns should I implement for offline support and authentication?▼

Implement offline capabilities using local caching patterns and secure authentication flows. Aligning these mobile and web UX patterns with platform-specific design guidelines ensures reliable accessibility and consistent user experience.

Does this domain knowledge cover platform-specific requirements for iOS and Android?▼

Yes, it provides structured mobile domain knowledge covering iOS and Android platform requirements. It includes performance considerations, accessibility guidelines, and design constraints to guide native and cross-platform architecture decisions.

When should I choose a progressive web app over a native mobile application?▼

Choose a PWA when web reach, responsive design, and rapid updates outweigh the need for deep hardware access. Native mobile apps remain superior for intensive performance, push notifications, and strict platform-specific UX patterns.

What performance considerations are critical when planning cross-platform mobile apps?▼

Critical performance considerations for cross-platform mobile apps include managing rendering bottlenecks, optimizing network payloads, and ensuring responsive design. Aligning these with platform requirements prevents UX degradation and supports scalable architecture.