skills.rest
Swear4
Swear4COMMUNITY
Explore all skills by this author →
GitHub

mobile-guidelines

Provides mobile MVP development guidelines covering feature toggles, API versioning, offline tolerance, and observability for B2B projects with mixed client versions.

Updated Aug 27, 2026
Search Tags:#offline#mobile#observability#mvp#api-versioning#b2b#feature-toggles
One-click install
npx skills add https://github.com/Swear4/agent_rules --skill mobile-guidelines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mobile-guidelines
Source: https://github.com/Swear4/agent_rules/tree/main/agent-universal/skills/mobile-guidelines
Command: npx skills add https://github.com/Swear4/agent_rules --skill mobile-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guide de bonnes pratiques mobile (MVP B2B) pour les développeurs et l'IA. Conçu pour aider les équipes à éviter d’être bloquées par des versions installées, réduire les tickets et maintenir une architecture évolutive sans sur-investissement dans les premières versions mobiles.

Core Features & Use Cases

  • Remote feature toggles (versionned, server-driven) pour activer/désactiver des fonctionnalités sans nouvelle release.
  • API versioning et tolérance multi-versions pour soutenir plusieurs clients en parallèle.
  • Messages in-app (maintenance/incident/update) avec des règles UX claires et des bannières informatives.
  • Règles de rétro-compatibilité et migrations locales du stockage pour éviter les crashs lors des updates.
  • Mise en œuvre d’un minimum online-tolerant (timeouts, retries, états UI explicites) pour une expérience stable en réseau instable.
  • Architecture côté serveur qui gère la logique métier critique, avec UI orchestrative côté mobile.

Quick Start

Apply these guidelines to design a B2B mobile MVP with feature toggles and multi-version support.

Frequently Asked Questions about mobile-guidelines

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

FAQPage Schema
What is the best way to handle offline resilience in a B2B mobile MVP?▼

Feature toggles for mobile MVPs should be remote, versioned, and server-driven to activate or deactivate functionality without new releases. This approach prevents client blocking and reduces support tickets while preserving a scalable architecture.

How do I display maintenance and incident messages in a mobile app?▼

Yes, these mobile MVP guidelines fit B2B projects with iterative releases and mixed client versions. They assume critical business logic resides server-side while the mobile UI acts orchestratively, requiring remote toggles and versioned APIs to prevent client blocking.

What is the best way to handle offline resilience in a B2B mobile MVP?▼

Offline resilience in a B2B mobile MVP requires an online-tolerant architecture with explicit UI states for connectivity, network timeouts, and retry mechanisms. This ensures a stable user experience even when operating on an unstable network.

How do I display maintenance and incident messages in a mobile app?▼

Display maintenance and incident messages using in-app banners with clear UX rules. Informative banners notify users of required updates or ongoing incidents without entirely blocking access to the application.

Related Skills

Explore More Software Engineering Skills→
armanisadeghiarmanisadeghi

api-route-auditor

Audit API routes for logic ownership, type safety, and validation.

Community
Advanced
FutureAtomsFutureAtoms
1

react-native-2026-state-management

Configure Zustand and TanStack Query for React Native state management.

Community
Advanced
bocanbocan
27

announcement-banner

Generate a configurable SwiftUI announcement banner system with remote JSON configuration.

Community
Advanced
memorysavermemorysaver

vercel-composition-patterns

Replace boolean props with explicit variant components and shared context in React.

Community
Basic