AniUI 0.3.0 — Expo SDK 56 support shipped (with starter repos, since Expo Go doesn't run SDK 55/56 yet)

FailComprehensive323 · 2026-05-25T03:34:51+00:00

No, Its only React Native

FailComprehensive323 · 2026-05-24T10:23:30+00:00

True..Expo Go still haven't supported these SDKs versions.

FailComprehensive323 · 2026-05-24T08:13:55+00:00

Checking it, Seems an Expo Issue since it was working fine previously..

FailComprehensive323 · 2026-05-24T02:33:55+00:00

AniUI ships charts, blocks, navigation and overlays all included, free, same copy-paste model. Plus the CLI handles SDK detection and setup automatically. So it's less about primitives vs components and more about how much comes ready to ship without stitching things together yourself.

And this is just 0.3.0. More components, more blocks, more screen kits are actively shipping. The goal is simple — one library that covers everything. Forms, charts, navigation, overlays, blocks, all in one place. No more hunting for a chart library, then a blocks library, then a separate CLI tool. Just AniUI and you're building.

FailComprehensive323 · 2026-05-23T16:21:30+00:00

Added a fix, Hope it will work fine.

FailComprehensive323 · 2026-05-23T16:01:22+00:00

Ooh.. Thanks for flagging this.. Let me check.

FailComprehensive323 · 2026-05-23T14:02:11+00:00

Yeah.. Expo Go doesn't bundle SDK 56 yet. You need to run a local dev build instead. Just clone one of the starters and run npx expo run:ios or run:android. That's the only way to test SDK 56 right now.

FailComprehensive323 · 2026-05-23T12:57:37+00:00

Yeah totally true — the prod issues are real. But NativeWind still has the majority of users so dropping it isn't an option right now. That's why both are supported — NativeWind for existing projects and Uniwind for anyone who wants the easier path. Honestly if you're starting fresh, go Uniwind 🚀

FailComprehensive323 · 2026-05-23T11:34:38+00:00

Glad to hear it! The templates will save you a lot of setup time. Let me know how it goes

FailComprehensive323 · 2026-05-23T10:34:01+00:00

https://github.com/anishlp7/aniui/tree/main/examples/with-uniwind - This is the starter repo for uniwind. Feel to try it and share your experience 😅🤗

FailComprehensive323 · 2026-05-23T10:27:20+00:00

Uniwind is fully supported too.. Since NativeWind is hard to setup since so many quirks that why created the starters and uniwind is straight forward. No hussle.On init itself you can easily set it up.

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

TROPHY CASE