A new BotanicBase, built on a foundation that can grow.
The original app proved the idea. The rebuild is about making the experience faster, more native, easier to update, and ready for everything BotanicBase wants to become.
What held it back
The old app had outgrown its first foundation.
Hardcoded content
Gardens, metadata, and image references lived in the app binary, so every content update required a new App Store build.
Fragile backend
The original backend depended on local infrastructure, which made reliability and scaling harder than they needed to be.
Dependency sprawl
Too many third-party packages made maintenance slower, riskier, and harder to reason about over time.
What changes now
The new app is built to feel native and stay fresh.
Native SwiftUI
The rebuild is designed around iOS-native navigation, animation, performance, and platform conventions from the start.
Cloud-managed content
Plants, gardens, tips, community content, and corrections can evolve without forcing users to wait for app review.
Cleaner foundation
A smaller, more intentional codebase makes BotanicBase faster to ship, easier to maintain, and safer to grow.
What this unlocks
Less patching, more building.
Faster everyday feel
Smoother scrolling, native transitions, and fewer layers between the app and iOS.
Better feature runway
Widgets, Shortcuts, deeper search, and platform features become much easier to support.
More responsive content
Gardens, plant details, care guides, and editorial fixes can improve continuously.
A note from the team
It is taking longer because the goal is not a fresh coat of paint. It is a clean start.
Same mission, better everything: fewer fragile dependencies, smoother iOS behavior, live content updates, and a product system that can keep expanding without dragging legacy weight behind it.
See what is coming