What's on Marqly's roadmap?

Marqly is actively developed, but there’s no public roadmap page and we don’t pre-announce features or ship dates. That’s deliberate: a promised feature that slips is worse than a shipped feature that surprises. The best way to see what’s new is to follow @getmarqly on X, where updates land as they release.

Why no public roadmap

Small teams building fast change direction when the evidence says to — a public roadmap either calcifies those decisions or turns into a graveyard of “coming soon” items that erode trust. We’d rather this FAQ stay honest than optimistic. What you read here describes the product as it exists today, not the product we hope to build.

How to influence what gets built

Email support@marqly.com with your use case. Not a feature name — the actual workflow: what you’re trying to do, where Marqly currently falls short, what you do as a workaround. Concrete requests from real users are the strongest signal the roadmap responds to, and a specific story routinely outweighs a dozen generic votes for the same feature.

What’s true today

Rather than promise futures, here are the current honest answers to the most-asked “when will you…” questions: there’s no public API, no Android app (the web app works in Android browsers), and no offline reading mode. None of that is a “never” — it’s a “not today, and we won’t pretend otherwise.” If any of those change, @getmarqly is where the announcement lands first.

The pattern to expect

Judge the pace by what has shipped rather than what’s teased: the product you can try right now at app.marqly.com is the roadmap’s track record. Signing up free — no card required — tells you more about where Marqly is headed than any feature list would.