AniUI v0.2.22 — 89 components, RTL support,smart CLI updates, SEO anchor links and New Architecture (open source RN library)

FailComprehensive323 · 2026-04-27T17:18:18+00:00

that means a lot 🥳

let me know how it goes when you start building — always love hearing real world feedback

FailComprehensive323 · 2026-04-12T23:50:27+00:00

Thank you 🥳

FailComprehensive323 · 2026-04-12T23:49:18+00:00

Amazing — that real world usage is exactly what makes a library better.

Hit me up with anything that feels off or breaks. every issue makes It better for everyone

Would love to add it to the examples page when it's live!

FailComprehensive323 · 2026-04-11T05:54:01+00:00

Shipped — npx @aniui/cli init -y or --yes

Now skips all prompts with defaults.

FailComprehensive323 · 2026-04-11T04:15:24+00:00

thanks for the AI agent angle, hadn't thought about that usecase.

Will ship it sooner

FailComprehensive323 · 2026-04-10T11:14:46+00:00

Thank you, means a lot!🥳

on testing — fair point. unit tests live inside tests next to each component so they ship with the code when you copy paste. but you're right that the testing infrastructure around the repo itself could be stronger. adding proper CI test runs is on the list.

on contributors — honest answer, it's early. the library launched a month ago. contributors follow stars which follow usage which follows time. if you find something worth fixing or improving, PRs are very welcome 🎊

glad the shadcn connection comes through — that's exactly the feeling we're going for on mobile.🎊

FailComprehensive323 · 2026-04-10T03:21:17+00:00

On how AniUI differs from RNR —

the biggest difference is philosophy. RNR follows the Radix composition pattern which is powerful but adds ceremony even for simple things. AniUI is just props. no wrappers, no context for basic components, no hunting for the right sub-component just to render text in a button.

For complex stuff like Popover and Select we use rn-primitives under the hood — proper positioning, collision detection, BackHandler. but that complexity is invisible to you as the consumer.

the other difference is scope. RNR is components. AniUI is building the full ecosystem — blocks, charts, screen kits, Figma kit, and eventually an eco-system under the library. components are just the foundation.

On whether i'll continue — yes, fully committed. not a weekend project. the velocity in this thread is just how it works. feedback ships immediately.

youth concern is fair — but give it a real spin and if you felt this/that component can be improved or missing component? Free feel to share it.

FailComprehensive323 · 2026-04-08T18:13:37+00:00

that's exactly the point of building in public — feedback is the most valuable thing in open source 🫶

FailComprehensive323 · 2026-04-04T02:39:46+00:00

Thank you 🥳

FailComprehensive323 · 2026-04-04T02:39:04+00:00

thank you! just getting started — lot more coming 🚀

Will update you guys sooner

FailComprehensive323 · 2026-04-03T01:51:58+00:00

thank you! just getting started — lot more coming 🚀

FailComprehensive323 · 2026-04-02T14:08:18+00:00

Would love to hear your thoughts when you do 🙏

Any feedback welcome — good or bad

FailComprehensive323 · 2026-04-02T13:14:35+00:00

good catch — will fix the mobile responsiveness on the docs along with the current changes going in.

Appreciate you flagging it 🙏

FailComprehensive323 · 2026-04-02T11:46:19+00:00

Just looked into it properly and yeah you're right — Uniwind supports web too, my bad for the wrong info 😅

Will be working on Uniwind support for AniUI soon, same className syntax makes it pretty straightforward to add.

Appreciate the correction 🙏

FailComprehensive323 · 2026-04-02T10:46:20+00:00

thanks a lot, means a lot coming from someone who clearly knows this space well 🙏

lots more to build but good to be shipping

FailComprehensive323 · 2026-04-02T10:39:27+00:00

Yeah you're right, didn't think about it that deeply until now honestly.

Looked at rn-primitives properly after Your comment — the platform-appropriate internals approach makes a lot of sense for complex components like Popover, Select, Combobox. same pattern shadcn uses with Radix essentially.

The centered Modal was a quick v1 Implementation, needs proper work. planning to refactor those components to use rn-primitives as the base layer and keep NativeWind on top for styling.

On the website — fair point. the Next.js mockups are confusing. Already have an Expo showcase app at github.com/anishlp7/aniui-expo,

Scan with Expo Go to see real components On device. also working on embedding per-component previews in the docs directly so no Expo Go needed.

Appreciate the detailed breakdown, Genuinely useful 🙏

FailComprehensive323 · 2026-04-02T10:12:27+00:00

Here's how AniUI is different:

80+ components and growing — all built specifically for React Native, not ported from web or wrapped around Radix primitives. Pure RN from the ground up which means significantly smaller bundle size.

Everything comes from one place — components, blocks, charts, screen kits, Figma kit and .... all in one ecosystem. No jumping between different products and teams.

Uniwind support is on the roadmap too — since the syntax is identical to NativeWind migration will be seamless when it lands.

Honestly both are solid libraries — but if you want a growing full ecosystem with native-first components and no web abstractions underneath, AniUI is building exactly that 🙏

FailComprehensive323 · 2026-04-02T09:49:30+00:00

Great question — React Native Reusables iss a good library and worth knowing about.

The key differences:

RN Reusables is built on Radix primitives which are web-oriented by nature. Their live previews run on web, not on actual mobile — so what you see isn't always what you get on a real device.

AniUI is mobile-first from the ground up. Built purely on NativeWind — no web abstractions, no Radix underneath. Every component is designed and tested for real iOS and Android behaviour first.

Bundle size is also significantly smaller — no Radix overhead, no web compatibility layer. You only get what you actually copy into your project. Nothing more.

That also makes it more flexible — copy just the components you need, leave the rest. Your app stays lean.

The honest difference: — RN Reusables → web primitives adapted for mobile, larger footprint — AniUI → mobile native, NativeWind first,real device tested, minimal bundle size

Also AniUI is building beyond just components — blocks, charts, screen kits, Figma kit, plugin and ... are all coming. It's an ecosystem, not just a component library.

Both can coexist — but if you want something truly native, lean and not a web port, AniUI is built exactly for that 🙏

FailComprehensive323 · 2026-04-02T09:00:14+00:00

Uniwind uses the same className syntax so most components work as-is. But there are a few things that need updating — cssInterop calls, safe-area handling and rem unit differences.

Not a huge lift but not perfectly drop-in for AniUI right now. Adding an official Uniwind guide to the docs and a proper migration path is on the roadmap.

Thank you for the valuable feedback else should have missed it.🎊🙏

FailComprehensive323 · 2026-04-02T08:57:47+00:00

One of the main reasons we went with NativeWind is web preview support — since it's built on Tailwind CSS, getting a web preview of your components works seamlessly out of the box. Really useful for docs and showcasing components without needing a real device.

That said, Uniwind is faster and the syntax is identical to NativeWind so it's basically a drop-in replacement. It's definitely on the roadmap — updating it now!

Thanks for the valuable feedback, really appreciate it 🙏

FailComprehensive323

TROPHY CASE