What's Next for rn-markdown-editor: New Components Coming in v1.0.21
Previously:
The core component set is stable and in active use, but we're not stopping there. Version v1.0.21 is currently in progress, and it's bringing a meaningful expansion to the primitive library. Here's a look at what's being built and what to expect from each addition.
DropdownMenu
A composable, fully themeable dropdown menu for contextual actions — the kind you'd attach to a "more options" button on a post card or toolbar. It will follow the same theming contract as the rest of the package, reading colors from useColors() so it fits into light and dark modes without any extra configuration. The API will be designed around composability: a trigger element, a menu container, and individual items, so you can slot in icons, destructive actions, or dividers without fighting the component's defaults.
Accordion
A collapsible section component for content that needs progressive disclosure — FAQs, settings panels, expandable post details. Internally it will use useDisclosure for the open/closed state per panel, keeping animations and state transitions predictable. The focus here is on smooth, native-feeling expand/collapse animation without pulling in a heavy dependency.
Avatar
An avatar component that displays a user's profile image when one is available, and falls back gracefully when it isn't. The fallback isn't just a grey circle — it extracts the user's initials from their display name and assigns a background color derived deterministically from the name itself, so the same user always gets the same color across sessions and devices without any stored preference. This makes the fallback genuinely useful in feeds and comment threads where profile images may not always load.
Card
A surface-level container component with consistent padding, border radius, and shadow/elevation that maps to the active theme's card and cardForeground tokens. Cards are the most common layout primitive in content-heavy apps and right now there's no dedicated component for one — you end up writing the same View wrapper with the same style object in a dozen places. Having a proper Card component eliminates that repetition and makes sure the surface color is always in sync with the active theme.
Radio
A single-select option group to complement the existing input primitives. Each option will have a proper touch target, a clear selected/unselected visual state using theme colors, and support for a disabled state. The goal is a component that feels native on both iOS and Android without requiring platform-specific branching in your own code.
When to expect it
All five components are currently in active development and targeting the v1.0.21 release. Once the release is published to npm, we'll put out a full post covering each component in detail — the same way we've covered the existing primitives — including API documentation, usage examples, and notes on any design decisions worth understanding.
We'll notify you here as soon as it lands.
System Reliability & Support
The development team remains committed to maintaining a secure, efficient, and highly optimized open-source toolkit. Continuous updates are actively deployed to ensure total cross-platform stability across iOS, Android, and Web deployments.
For technical assistance or to report issues, please submit on the comment or our official NPM Project Page.
Thanks for your time and support. Let's make Steem great, again.
Official NPM Link: https://www.npmjs.com/package/rn-markdown-editor
Primary Architecture: TypeScript / JavaScript
Supported Environments: Expo & Bare React Native CLI
Utility Exports: useDebouncedInput, useDisclosure, useMergeState