Homepage Mistakes Costing Small Businesses Leads
A practical homepage teardown for small business websites: the mistakes we see most often, why they matter, and what to fix first.
Read article"Should we build in React Native or go native?" It's one of the first technical questions startup founders ask, and it often gets answered by whoever they happen to speak to first. Agencies with React Native teams say React Native. Swift developers say native. Neither answer is necessarily wrong — but both need a lot more context.
This is an attempt at an honest guide for non-technical founders making this decision. No hype in either direction.
What React Native actually is
React Native is a framework, maintained by Meta, that lets you write one JavaScript codebase and compile it into apps for both iOS and Android. It's not a web app wrapped in a browser view — it renders real native components. A React Native button is a real iOS UIButton or Android Button, not an HTML element styled to look like one.
The practical result: React Native apps look and feel like native apps for most use cases, and your development team is writing one codebase instead of two.
Expo is a layer on top of React Native that further simplifies development and deployment. For most new projects, starting with Expo is the sensible choice — it handles the native build toolchain, provides over-the-air updates, and reduces the setup overhead significantly. When you need access to a native API that Expo doesn't support, you can "eject" to a bare React Native project.
Where React Native wins
- Speed of development. One codebase, one team, one set of business logic. For most app categories — marketplaces, SaaS tools, social apps, booking platforms, productivity apps — React Native delivers the full feature set much faster than building two separate native apps.
- Team availability and cost. There are far more JavaScript/React developers than Swift or Kotlin specialists. React Native talent is more accessible and, in most markets, less expensive.
- Shared backend integration. If your team already uses JavaScript or TypeScript on the backend (Node.js), sharing code, types, and validation logic between your API and your app reduces errors and speeds up development.
- Over-the-air updates. With Expo's update mechanism, you can push UI and logic updates to users without going through the App Store review process. For rapidly iterating startups, this is a meaningful operational advantage.
- MVP and seed stage builds. If you're building to validate a concept, raise a round, or get your first users, React Native is almost always the right starting point. Ship faster, learn faster, iterate faster.
Where React Native struggles
- Hardware-intensive features. Bluetooth Low Energy, NFC, custom camera pipelines, real-time audio processing, AR — React Native can access many hardware APIs, but the abstractions sometimes leak. Complex hardware integration often requires writing native modules in Swift or Kotlin anyway, at which point you're partly doing native development through the back door.
- Highly complex animations. React Native's animation system is capable, but building genuinely fluid, gesture-driven interfaces — the kind that feel like they were designed natively for the platform — is harder in React Native than in Swift/UIKit or Kotlin/Jetpack Compose. The gap has narrowed considerably with the New Architecture (JSI, Fabric renderer), but it exists.
- Deep platform-specific features. Apple Pay and Google Pay work. But deep integrations with platform-specific APIs — HealthKit, CarPlay, Android widgets, app clips — require native code. If your product is deeply integrated with platform-specific capabilities, you'll end up writing a lot of native modules.
- Long-term maintenance. React Native moves quickly. Major architectural changes (the New Architecture, Hermes engine, Fabric) require periodic migration work. Native iOS and Android have much more stable APIs over time.
When native iOS/Android is the right call
- Hardware-intensive applications. Medical devices, industrial IoT, custom camera or audio applications where performance at the hardware level matters. Native gives you the full SDK, the full performance ceiling, and the full debugging toolchain.
- High-performance games and real-time graphics. If your app is graphically intensive — game engine level — you're looking at Unity, Unreal, or native Metal/Vulkan. React Native isn't the tool for this.
- App Store feature parity is a differentiator. If being the first app on the market to support a new iOS feature is strategically important, native gives you day-one access.
- Long-term, well-funded product. If you have the budget for two separate teams and the app experience quality is core to your competitive position, native gives you the highest ceiling.
The decision framework
For most startup founders, the decision looks like this:
- MVP or early-stage product with standard feature set: React Native with Expo
- Consumer app where fluid, premium UX is a core differentiator: Native
- B2B or internal tool: React Native
- Hardware-dependent product (Bluetooth, NFC, custom sensors): Native or React Native with custom native modules
- Game or real-time graphics: Unity/Unreal or native
At Shro Web, we build in both React Native and native — and we'll tell you honestly which one fits your project, not which one fills our schedule. If you're at the planning stage and want to talk through your options, get in touch.