feat: added React Native Renderer#42
Merged
Merged
Conversation
ssmrmmk
approved these changes
Jul 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds
@mobile-reality/mdma-renderer-react-native— a React Native rendering layer for MDMA, a sibling to@mobile-reality/mdma-renderer-react. It renders all 9 MDMA component types plus inline Markdown as native iOS/Android UI, reusing the existing headless stack (spec+runtime) unchanged and reimplementing only the view layer with RN primitives (dispatch, bindings, component state, policy, audit, and PII redaction all come fromruntime).Also adds
demo-native/— an Expo (SDK 54) example app: a provider-agnostic MDMA agent built on the Vercel AI SDK (OpenRouter / Anthropic / OpenAI, keys via.env). It mirrors the web Agent Chat's sub-agent/brief flow — the conversation model calls agenerate_mdmatool with a brief, a separate author call produces the document, and it's rendered withrenderer-react-native. Runs in Expo Go (core RN components only, no custom native modules).Closes #
Type of Change
Packages Affected
@mobile-reality/mdma-spec@mobile-reality/mdma-parser@mobile-reality/mdma-runtime@mobile-reality/mdma-attachables-core@mobile-reality/mdma-renderer-react@mobile-reality/mdma-prompt-pack@mobile-reality/mdma-renderer-react-native(depends onspec+runtimeonly; no changes to existing packages)@mobile-reality/mdma-demo-nativeChecklist
pnpm lintpasses for the new package).pnpm test).pnpm typecheck).pnpm changeset) if this change affects published packages.sensitive: truewhere appropriate. (Renderer honorssensitivefrom the spec — form inputs usesecureTextEntry, table cells mask.)How to Test
Renderer package
pnpm --filter @mobile-reality/mdma-renderer-react-native buildpnpm --filter @mobile-reality/mdma-renderer-react-native typecheckpnpm --filter @mobile-reality/mdma-renderer-react-native testExpo demo app (real agent, needs an API key)
cp demo-native/.env.example demo-native/.envand set one key (e.g.EXPO_PUBLIC_OPENROUTER_API_KEY=…).pnpm --filter @mobile-reality/mdma-demo-native start --cleari/afor a simulator).TODO
Add wider test coverage