Documentation Index
Fetch the complete documentation index at: https://docs.replyke.com/llms.txt
Use this file to discover all available pages before exploring further.
Styling Variants
Understanding inline styles vs Tailwind CSS variants and when to use each.Comparison
| Aspect | Inline Styles | Tailwind CSS |
|---|---|---|
| Dependencies | None | Requires Tailwind CSS |
| Dark Mode | theme prop | dark: prefix |
| Customization | Change hex codes | Change classes or config |
| Code verbosity | More verbose | Concise |
| Learning curve | Easier | Tailwind knowledge needed |
| React Native | ✅ Supported | ✅ (NativeWind) |
Inline Styles
- No additional dependencies
- Works everywhere (web and React Native)
- Explicit, self-contained styling
- Direct control over every value
- More verbose code
- Manual dark mode logic in every component
- Repeated color values across files
- Projects without Tailwind
- React Native / Expo apps
- Developers who prefer explicit styles
Tailwind CSS
- Concise, readable code
- Automatic dark mode with
dark:prefix - Integrates with design systems
- Smaller bundle with purging
- Requires Tailwind CSS installed
- Learning curve if unfamiliar
- Less explicit (need to know what classes do)
- Projects already using Tailwind
- Web-only React apps
- Developers who prefer utility-first CSS
Choosing a Variant
Choose duringnpx @replyke/cli init:
Switching Variants
To switch after installation, delete the component and reinstall with the new style:React Native Styling
For React Native and Expo:- Inline Styles → Standard React Native
StyleSheet/styleprop approach - Tailwind → Uses NativeWind (
classNameprop)
Next Steps
Colors & Theming
Customize colors
Layout & Structure
Modify layout
Adding Features
Add custom functionality
Advanced
Advanced techniques

