We finally launched JustBlogged 🎉 Looking for honest feedback
Hey everyone!
After months of work, my co-founder Usama Ejaz and I have officially launched JustBlogged.
The goal is simple: make blogging feel fast, modern, and enjoyable without unnecessary complexity.
We're still in the early days, and instead of assuming what users want, we'd rather learn directly from the community.
If you have a few minutes, we'd really appreciate honest feedback.
Website:
https://justblogged.com
A few questions:
- What stands out to you first?
- Is there anything confusing?
- What's one feature you'd want before using it regularly?
We'll read every reply and use it to shape our roadmap.
Looking forward to your feedback!
"Nicer to write in" versus "solves a publishing problem I couldn't solve elsewhere" is a genuinely useful way to sort feedback, the first one is a compliment, the second one is an actual reason someone would switch and stay. Curious which one you're hearing more of so far now that the migration-trigger question is out there.
The pushback about needing a specific migration trigger is the sharper question, "what's confusing" gets vague answers, but "what would make you actually switch from what you use now" forces someone to reckon with their real switching cost. A simpler editor alone rarely beats existing habit, there has to be something people are actively annoyed by right now that this fixes. What's the one complaint about existing blogging tools you're hearing most often from people who've tried this?
That's a really valuable distinction. So far, we're hearing more about simplifying the writing experience, but we're actively trying to uncover the deeper publishing problems that would actually make someone switch. One theme that's coming up repeatedly is reducing friction from writing to publishing but we still have a lot to validate. Really appreciate you pushing us to think beyond the editor.
Reducing friction from writing to publishing is a real theme worth chasing, that's much closer to an actual switching reason than "nicer editor." Good sign you're already hearing it repeat instead of just once. What does that friction usually look like for people, is it more about formatting and cleanup before publishing, or the actual step of getting it live somewhere?
So far, it's been more about everything around publishing than writing itself. Formatting, final cleanup, SEO-related tasks, and getting content ready to go live. We're still validating it, but that's the pattern we're seeing most often so far.
Everything around publishing rather than the writing itself lines up with what a lot of blogging tools miss, they optimize the part that was never really the bottleneck. Formatting, cleanup, and SEO prep sound like the boring, unglamorous parts that quietly eat the most time before something goes live. Is the plan to automate those steps away entirely, or just make them faster and less annoying to do manually?
That's the direction we're exploring. We don't want to automate for the sake of automation, but wherever repetitive publishing tasks can be simplified without taking control away from creators, that's where we think the biggest value is. Still validating exactly where that balance should be.
The three feedback questions are broad before you've named the migration trigger. Pick one platform users already write on and say exactly what breaks there: ownership, export, SEO, or workflow. Otherwise the replies will mostly optimize the editor while the switching cost stays untouched.
That's great advice. We've started asking more switch-focused questions instead of general feedback because you're right, the real challenge isn't improving the editor, it's understanding what would make someone leave an existing platform. We'll definitely be more intentional about validating that.
The interesting challenge isn't making blogging simpler—it's giving people a compelling reason to start on JustBlogged instead of the platform they're already using. I'd keep validating whether users stay because the writing experience feels better or because the product solves a publishing problem existing platforms don't.
That's a great point, and it's something we've been discussing a lot. A better editor alone isn't enough to make people switch. Our focus is on solving real publishing pain points, and conversations like this help us validate what actually matters. Really appreciate the insight!
That makes sense.
One thing I'd keep watching is whether users describe the switch as "this is a better place to write" or "this solves a publishing problem I couldn't solve elsewhere."
The second is usually what creates a reason to leave existing habits.
Absolutely. That's a distinction we don't want to lose sight of. A better writing experience is valuable, but solving a publishing problem is what creates a real reason to switch. That's exactly what we're trying to validate over the next few weeks.
Exactly.
The interesting signal will be whether users can clearly name the publishing problem they couldn't solve elsewhere.
That answer will probably tell you more than feature feedback alone.