One Spec. Every Role. Native Power Without the Chaos.
A spec-driven React Native and Expo system built to forge enterprise mobile apps, multi-role experiences, and native workflows from one coherent foundation.
Stop rebuilding apps for every role. Start delivering complete mobile experiences.
One architecture. Every role. A truly native experience.
Mobile products often fragment into separate apps, duplicated business logic, inconsistent screens, and platform-specific workarounds that grow harder to maintain with every release.
Mobile Forge replaces that fragmentation with declarative specifications and a reusable, brand-neutral core. Screens, features, access, and navigation follow shared contracts, while each product retains its own identity and native capabilities.
The ambition: build once where logic is shared, specialize where the device demands it, and never sacrifice the experience.
The latest release — checksummed, attested, one command per platform.
mobilex-installer unpacks the release's source into ./mobilex.
Linux and macOS:
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/comstrx/mobilex/releases/latest/download/mobilex-installer.sh | shWindows (PowerShell):
& ([scriptblock]::Create((irm https://github.com/comstrx/mobilex/releases/latest/download/mobilex-installer.ps1)))From source:
git clone https://github.com/comstrx/mobilex.git
cd mobilex
bun install --frozen-lockfile
bun run startEvery asset carries a .sha256 sidecar and build provenance: gh attestation verify <asset> --owner comstrx.
A continuously evolving system for demanding mobile applications.
Spec-Driven Screens & Features · Multi-Role Navigation · Authentication & Secure Sessions · Typed APIs & Realtime · Offline Storage & Synchronization · Forms, Validation & UI States · Maps, Media & Device APIs · Notifications & Deep Links · Localization, RTL & Themes · Native Performance & Release Optimization
From customer storefronts to operational dashboards and delivery workflows, every experience follows the same engineering language.
One vocabulary. Every role. Endless possibilities.
Declare the experience. Share the intelligence. Respect the platform.
Product Specs · Identity · Roles
│
Spec Compiler
│
Screens · Blocks · Features
│
React Native · Expo
│
Shared Bun Foundation
│
Native Adapters · APIs · Storage
Single Responsibility · Unidirectional Dependencies · Typed Contracts · Brand-Neutral Core · Native Independence
Specifications own product configuration. Mobile Forge owns navigation, rendering, and native interactions. Shared TypeScript logic lives in the Bun foundation; device-specific behavior stays behind explicit adapters.
No duplicated business logic. No tangled screens. No forced browser abstractions.
Not another collection of screens. One coherent mobile system.
Every feature has a clear owner, declared inputs and outputs, predictable error states, and a focused public interface. Navigation, data access, offline behavior, and UI composition remain separate concerns—not one giant component.
Common contracts are reused across web and mobile without pretending that native views are DOM elements. The mobile layer stays free to exploit platform capabilities while preserving consistent data, validation, localization, and design language.
Maximum reuse. Minimum coupling. Absolute architectural discipline.
Launch fast. Scroll smoothly. Ship lean.
Lazy Module Loading · Lean Native Dependencies · Virtualized Lists · Efficient Assets · Image Caching · Render Isolation · Memory Discipline · Minimal Bundle Weight · Responsive Navigation
Performance is measured where users feel it: cold start, frame drops, memory, application size, battery impact, and real interaction latency—on actual devices, not just simulators or synthetic benchmarks.
Every optimization must earn its complexity through repeatable evidence and preserve a complete, reliable experience.
Fewer wasted bytes. Fewer dropped frames. More native speed.
Every session isolated. Every permission intentional. Every boundary enforced.
Secure session storage, scoped offline data, controlled background work, explicit device permissions, protected transport, and validated input shape the application from the start.
Queued operations must never cross user identities. Sensitive values stay out of bundled configuration, and presentation-level access rules never replace authorization by the owning backend.
No leaked sessions. No cross-user replay. No security by appearance.
Build with discipline. Verify on devices. Evolve with confidence.
Strict linting, type safety, spec validation, contract tests, production exports, and targeted device measurements protect the reusable core without turning every change into an expensive rebuild.
bun run check
bun run typecheck
bun test
bun run exportDevice performance: bun run perf · bun run compare.
Engineering excellence isn't a milestone. It's the standard.
Copyright © 2026 Abdulrahman Yasser (comstrx).
Licensed under the Apache License 2.0.