Why I Started the Tropera Blog (And What It Means for You)

I love romance. Small-town, hockey, contemporary, the ones that make you set the book down on your chest and just breathe for a second. But finding the right one for the mood I was in was never as easy as it should be.

Genre doesn't tell you enough. "Romance" could mean a slow burn that takes 300 pages to get to a hand touch, or a spicy enemies-to-lovers that starts throwing sparks by chapter three. Bestseller lists tell you what's popular, not what fits the specific ache you're carrying that week, the one where you want comfort, not heartbreak. Or forced proximity, not friends-to-lovers. Or something set in a snowed-in cabin because it's July and you're pretending it's not.

BookTok and Bookstagram help, genuinely. But scrolling for the right recommendation can turn into its own kind of reading slump, the algorithm-induced kind, where you close the app having read zero pages and absorbed forty trope debates instead.

I started building Tropera because I wanted a place that starts with the mood, not the metadata.

I want to be honest with you here, because I think that's the whole point of this blog: Tropera is not a finished app. It's not sitting in the App Store waiting for you to download it. Right now, it's me, mostly self-taught, learning FlutterFlow and Firebase one tutorial and one mistake at a time, building this thing from the ground up.

That's genuinely part of the story I want to tell here. Not just "here's what Tropera will be someday," but "here's what it actually looks like to build a book discovery app with no engineering background, a lot of stubbornness, and a very specific vision of what reading should feel like."

Some weeks that means sharing a small win, a feature that finally works, a database structure that finally makes sense. Other weeks it might mean admitting something broke and I had to start over. I'd rather show you the real, slightly messy middle than pretend this appeared fully formed.

Because building in public only works if there's actually a public to build with.

I want this blog to be a few things at once. Sometimes it'll be behind-the-scenes — the "Building Tropera" diary entries where I talk through decisions, setbacks, and what's coming next. Sometimes it'll be pure book talk, mood breakdowns, trope deep-dives, "what to read if you're in a reading slump" type posts, the kind of conversation I'd want to have with a friend who also has a book thoughts note she has no one to send.

And sometimes it'll just be an invitation. Because the real goal of Tropera isn't only "an app that recommends books." It's a community. A place where mood readers, trope lovers, and people who take their comfort reads seriously feel like they belong. The app is one piece of that. This blog, honestly, might be where the community starts before the app even exists.

I don't want to build this alone in a corner and hand you a finished product one day. I want you here for the messy middle, the part where your input actually shapes what this becomes.

So here's my soft ask. If any of this resonates, if you've ever wanted a book discovery space that starts with "I need something cozy and low-stakes" instead of "here are this month's bestsellers", I'd love to hear from you.

Join the waitlist, so you're first in line when Tropera opens up. Come tell me, in the comments or on Instagram: what kind of book discovery space do you wish existed? What mood are you in right now, reading-wise? I read every single one.

This blog is the start of that conversation. Glad you're here for it.

Love,

Maïka xxx