Common questions, direct answers.
Everything you might want to know about VibeKit Native, how the CLI works, and how it fits into your Expo workflow.
- 01
What is VibeKit Native?
VibeKit Native is a registry of 65 production-ready React Native components for Expo apps. Each component installs with a single npx command (npx vibekit-native install <name>) and drops into your project as an editable TypeScript file. All components share a dark-only design system with NativeWind v4 styling — consistent out of the box.
- 02
How is this different from a component library like NativeBase or Tamagui?
Those are full UI libraries you install and import from node_modules. VibeKit Native installs each component as a plain file in your project — you own the code completely. No version lock-in, no breaking updates from upstream, no dependency on a CDN. And since each component is a single file, AI agents can read, understand, and extend them instantly.
- 03
Does VibeKit Native work without Expo?
No — the components are built for Expo SDK 55+ with expo-router and NativeWind v4. If you're using bare React Native CLI without Expo, you'd need to adapt the file structure and navigation patterns yourself. We recommend Expo for new projects.
- 04
Is VibeKit Native free?
Yes, MIT licensed and free to use forever. You'll pay for the services your app uses — EAS Build credits for store deployment, Neon for cloud database, Better Auth for authentication — most of which have generous free tiers.
- 05
What tech stack does VibeKit Native expect?
Expo SDK 55+, TypeScript, NativeWind v4, expo-router, TanStack React Query, Zod + react-hook-form, Zustand, @expo/vector-icons, react-native-reanimated, @shopify/flash-list, and EAS Build for deployment. Components follow these conventions but work with any stack — they're just files in your project.
- 06
Do I need to set up a design system or theme first?
No. Every component ships with the dark-only design system built in — indigo accent, zinc borders, 12px default radius, consistent spacing. Install any component and it matches every other component immediately. No ThemeProvider, no CSS variable setup, no theme switching.
- 07
What categories of components are available?
Seven categories: Auth (login-screen, register-screen, forgot-password-screen, verify-otp-screen, new-password-screen, complete-profile-screen), Home (hero-banner, section-header, category-circles, flash-sale-timer), Commerce (product-card, cart-item, price-display, order-card, order-timeline, product-header), Chat (chat-bubble), Profile (points-card, coupon-card), Shared (screen-header, filter-sheet, filter-sort-bar, search-bar), and UI (button, input, badge, avatar, card, bottom-sheet, toast, skeleton, rating, otp-input + more).
- 08
Can I install multiple components at once?
Yes — npx vibekit-native install auth installs all auth components. You can also pass multiple names: npx vibekit-native install login-screen product-card chat-bubble. Category names install everything in that category.
- 09
How do I customize a component after installing it?
Edit the file directly at src/components/<category>/<name>.tsx. It's a plain TypeScript file with NativeWind classes — tweak the JSX, change the styling, wire your API. No registry lock-in. Delete the file if you don't need it anymore. It's your code.
- 10
Is there a dark mode or light mode?
Dark-only by design. Every component ships with the complete dark palette — no light mode variants, no theme switching, no .dark conditional classes. This eliminates an entire class of bugs (wrong contrast, unreadable text, inconsistent backgrounds) and keeps every component predictable.
- 11
How do database and ORM work in VibeKit Native?
VibeKit Native components don't enforce a specific database — they're just UI files in your project. Use whatever data layer you prefer: TanStack Query with any backend, local state with Zustand, or a database with expo-sqlite, Supabase, or Firebase. The components are agnostic.
- 12
Can I use VibeKit Native with Claude Code, Cursor, or other AI agents?
Absolutely. Every component follows consistent patterns — Zod schemas, react-hook-form wrappers, NativeWind classes — so AI agents read and extend them instantly. Install a component, tell your agent to wire it to your backend, and it ships. The predictable structure means agents spend zero context guessing your conventions.
- 13
How do I deploy an app built with VibeKit Native?
Use EAS Build: eas build --profile production compiles your native binaries. Then eas submit sends to the App Store and Google Play. For frequent updates, eas update pushes OTA JavaScript updates that users get on next app open — most changes never need a store review cycle.
- 14
What if a component doesn't do exactly what I need?
Edit the installed file. Every component is a starting point — change the validation, swap the icons, adjust the layout. The dark design system tokens are consistent across all components, so your customizations still match the rest of the app. If you build something generally useful, open a PR to contribute it back.
- 15
Where do I get help if something breaks?
Open an issue on the GitHub repo (github.com/MUKE-coder/vibekit-native), reach out via the JB website (jb.desishub.com), or post in the Desishub WhatsApp community. For Expo-specific issues, the Expo Discord is more responsive than we are.