AniUI 0.7.0 — 148 components, gooey animations, new carousels, and foldable UI coming next (free, open source, shadcn-style for React Native)

Anish L — Fri, 11 Sep 2026 07:43:10 +0000

For anyone who hasn't seen it: AniUI is a shadcn/ui-style component library for React Native. You don't npm install it — you copy the component source straight into your project via CLI:

npx @aniui/cli add button

You own the code, customize whatever you want, no black-box dependency. Built on Uniwind (new default, 2-3x faster than NativeWind) or NativeWind, rn-primitives for accessibility, strict TypeScript, zero StyleSheet.create.

148 components now. Still fully free, MIT licensed, supports Expo SDK 54 through 57 plus bare RN 0.76+.

0.6.0 — AutoComplete + full docs overhaul

New AutoComplete component — free-text input with inline filtered suggestions. Distinct from Combobox's modal-select and SearchBar's no-suggestions approach. Three different components for three different use cases.

Swept 9 components that fell under the 48dp minimum touch-target rule — PromptInput, Stepper, Select, DropdownMenu, Calendar, Menubar and more. Added a lint script so it can't regress.

Docs sidebar rebuilt from one flat 94-item list into 8 collapsible purpose-based categories.

Every component's doc page now pulls its source snippet live from the actual file — no more hand-copied stale code blocks.

Unified all code blocks onto Shiki with real dual light/dark themes.

0.6.1 — Demos that look like real apps

Rewrote all example-app demos from generic prop galleries into realistic screens — settings pages, checkout flows, a full ChatGPT-style chat composer, a swipe-to-archive inbox, dashboards.

Fixed Select, Popover, Tooltip, HoverCard and DropdownMenu all opening with a weird extra offset. The accessibility layer was measuring the forced 48x48 touch-target box instead of the actual trigger content.

Docs site no longer flashes light mode before switching to dark on load.

0.7.0 — Gooey animations + new carousels

2 new carousels:

Vertical Flow Carousel — tap-to-focus stack with tilt, scale and blur on neighbors.

Vertical Page Carousel — full-bleed vertical pager with haptics.

New gooey/morph family:

Morph FAB, Gooey Popover, Gooey Search Tabs — shapes that blob-merge into each other on interaction. The kind of animation you'd expect from a native app, not a React Native one.

Bug fixes: Rounded card corners getting clipped into a plain rectangle on one carousel. Curved bottom-tab bar drifting and clipping its notch near screen edges. Draggable icon dock mis-mapping touches with padding. Bottom-sheet Tray that would open once and silently fail to reopen — a Modal remount race on Android.

Docs sidebar reorganized by what a component actually is — dedicated Buttons section, Carousels promoted to top-level, consolidated Loaders section.

What's next — foldable UI

Apple just launched the Duo — their foldable iPhone. Samsung has had foldables for years.

Next up for AniUI: adaptive components that respond to fold state. Components that flip, unfold and reflow naturally as the device opens and closes.

Nobody in the React Native ecosystem is building for foldables properly yet. We're changing that.

Docs: aniui.dev

GitHub: github.com/anishlp7/aniui

Happy to answer questions or take feature requests — always looking for what's missing.

I built shadcn/ui for React Native— here's why and what I learned

Anish L — Tue, 31 Mar 2026 17:45:53 +0000

Every time I started a new React Native project, I faced the same frustration. On the web I had shadcn/ui — copy-paste components, own the code, customize everything with Tailwind. On React Native I had two choices: install a heavy npm package and fight abstractions every time I needed to tweak something, or build every component from scratch and waste the first week of every project on buttons and inputs.

Neither felt right. So I built a third option.

What is AniUI?

AniUI is an open source React Native component library that takes the same approach as shadcn/ui. Copy-paste components directly into your project, own every line of code, and customize freely with NativeWind. No lock-in, no surprise breaking changes, no fighting abstractions.

Docs: aniui.dev
GitHub: github.com/anishlp7/aniui

Why copy-paste instead of npm install?

When you install a component library as a package you're locked into their versioning, deep customization means fighting their abstractions, and updates can break your UI unexpectedly. When you copy-paste, the code lives in your project. You own it completely. Customize anything without workarounds.

shadcn/ui proved this model works brilliantly for web. AniUI brings the same philosophy to React Native.

What's inside right now?

Phases 1 and 2 are complete with 50+ components including buttons, inputs with leading/trailing icons and password toggle, modals, bottom sheets, toasts, cards, badges, avatars, skeleton loaders, OTP input, swipeable list item, stepper, FAB, empty state and action sheet.

Phase 2 added charts (line, bar, pie, area), pre-built blocks for auth, dashboards, settings and onboarding, plus an examples folder with working setups for Expo 54, Expo 55 and bare React Native.

Every component has unit tests living inside tests right next to the code — copy the component, the tests come with it.

How it's different from NativeBase or Gluestack?

These are solid libraries and I have nothing against them. The difference is philosophy. With AniUI you own every line of code, bundle size is only what you actually use, and NativeWind customization is native — no workarounds needed.

What's coming next

Phase 3 is a Figma UI Kit — every component in Figma, pixel perfect match to the code, launching on pro.aniui.dev.

Phase 4 brings premium screen kits for auth, onboarding, e-commerce, dashboards and social apps.

Phase 5 is a Figma plugin to export designs directly as AniUI components.

Phase 6 is something big — building in public, you'll see 👀

What I learned:

The community shapes the product more than any roadmap does. After posting Phase 1 on Reddit the feedback was specific and actionable — tests, theming docs, input icons, Android behaviour. All of it made it into Phase 2. Build in public and listen to developers using it in real projects.

Copy-paste is also harder to build than npm packages. Every component needs to be completely self-contained with zero hidden dependencies. Worth it for the developer experience though.

The best way to try AniUI is to scan the Expo Go QR code in the showcase app and see everything running on your real device.

Docs: aniui.dev
GitHub: github.com/anishlp7/aniui
Showcase: github.com/anishlp7/aniui-expo

If this resonates with frustrations you've felt in React Native — give it a star. It helps more than you know 🙏

Building AniUI fully in public — follow along on X @anishlp7

DEV Community: Anish L

AniUI 0.7.0 — 148 components, gooey animations, new carousels, and foldable UI coming next (free, open source, shadcn-style for React Native)

I built shadcn/ui for React Native— here's why and what I learned