Why I'm leaving WordPress and switching to Firebase to develop for the Hispanic travel market ✈️
After 40+ articles and seeing the first signs of traction (30+ monthly visits and 7 subscribers), I’ve made a big decision for Viajahoytips: I’m moving from WordPress to Firebase.
WordPress was great to validate the idea, but as I shift from a "reading destination" to a "utility tool" (like my new flight planning feature), I need more control and speed.
Why the change?
Customization: I’m building logic for real-time flight updates and custom alerts. Firebase gives me the flexibility to handle user data and real-time triggers much more efficiently than a standard WP setup.
Learning Curve vs. Scale: I want to own the stack. Moving to Firebase is a bet on the long-term scalability of the "app" side of my project.
The "Why" behind the niche: A lot of people ask me: Why travel for legal Hispanic residents in the US? The answer is simple: Trust. Most content out there is in English or generic Spanish from other countries. My audience needs to know the specific nuances of traveling within and from the US with their specific legal status. They don't just need a blog; they need a companion tool that speaks their language—literally and culturally.
Current status:
Tech: Mid-migration. Learning a lot about NoSQL while keeping the SEO juice from my 40+ articles alive.
Growth: Still 100% organic. Trust is our currency.
Question for the devs & makers: For those who started with a CMS and moved to a custom stack: What was your biggest "I wish I knew this before" moment during the migration? And for the travelers: Does a "custom alert" for document expiration sound like a lifesaver or just another notification?
