简体中文
English
Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Saga?
Saga is a connected workspace for notes, documents and tasks, where pages can be organised into collections and linked to one another. Its public feedback board, Saga Feedback, shows how the product is being shaped: open feature requests cover tables, tasks, sharing, export, offline access and Saga AI, with a roadmap section tracking what is planned, in progress and complete.
What the feedback board reveals about how people use it
The requests cluster around a few concrete jobs, which is a useful guide to where Saga fits:
- Writing and structuring knowledge: collapsible headings, callouts, code blocks and table formatting point to long-form notes and technical documentation.
- Organising work: Kanban views, task status fields, task tags, pinning tasks and sorting tables suggest people run projects and to-do lists alongside their notes.
- Getting information back out: PDF export, sharing collections, workspace-wide AI search and version history are all about retrieval and distribution.
- Working away from a desk: an iOS app and offline mode are both requested, so mobile and disconnected use is clearly on users' minds.
Who it suits, and the trade-offs
Saga is most appealing to individuals and small teams who want notes and lightweight task tracking in one place rather than stitching together a separate docs tool and a project tracker. The trade-off is maturity: several capabilities people commonly expect — offline mode, a mobile app and workspace-wide AI search — appear on the board as requested or in progress rather than finished, so anyone who depends on those should check current status before committing.
A practical next step: open the board, filter by "Complete" to see what has shipped, then compare the "Planned" and "In Progress" items against the features you cannot work without. If, say, offline access is essential for you, that single filter will tell you more than any feature list.
How do I submit a feature request or feedback to the Saga team?
Use Saga's public feedback board at Saga Feedback: search the existing Feature Requests board first, then add your idea as a new post or upvote and comment on an existing one. The board is grouped into Feature Requests and Roadmap, with items marked Planned, In Progress or Complete, so you can see whether your idea is already tracked before posting.
A practical submission routine
- Search before posting. Check the board for close matches — for example, "Offline mode," "API," "Share collection," "Version history" or "iOS mobile app" — and add your vote or detail there instead of splitting support across duplicates.
- Title it as a capability, not a complaint. "Sortable tables" or "Full RTL support" tells the team what to build; "tables are annoying" does not.
- Describe the workflow, not just the wish. Say what you were doing, where Saga got in the way, and what a good outcome looks like. A concrete example — pasting cells from a spreadsheet and needing column widths to hold — is more actionable than a general request.
- State who it affects and how often. A daily irritation for a small team reads differently from a once-a-quarter need for a large one; both are useful, but the team needs to know which.
- Add workarounds you have tried. If you already export to another tool or keep a separate list, that tells the team how much friction the gap creates.
What makes feedback land
Requests on the board are visible to other users, so votes act as a rough signal of shared demand. That rewards clear, broadly relevant posts over private edge cases. If your need is specific to your organisation, explain the general pattern behind it so others can recognise themselves in it.
Use the Roadmap view to calibrate expectations: items under Planned and In Progress are already committed, so feedback there is most useful as refinement — edge cases, constraints, how you would test it. Items still in Feature Requests are where new arguments carry the most weight.
A quick decision criterion
- Already listed? Vote and comment with your use case rather than creating a near-duplicate.
- Not listed? Post it with a capability-style title, a worked example and your frequency of need.
- Urgent and blocking? The public board is a product-planning channel, not a support queue; for account or access problems, use Saga's official support route instead.
As a next step, draft your post in three sentences — the capability, the workflow it unblocks, and how often you hit the gap — then search the board once more before submitting.
Which features are currently planned versus in progress on Saga's roadmap?
Planned items on Saga's public roadmap are the ones marked "Planned," while "In Progress" items are already being built. Based on the current board, the split is:
Planned
- Ability to multi-select pages as tags in a collection from other collections
- Mention collection as context in Saga AI
In Progress
- Saga AI search across your workspace
- iOS mobile app
A quick way to read this: "Planned" means the team has committed to the idea but work hasn't started in earnest, so timing is looser and scope may still shift. "In Progress" means active development, making those two the nearer-term arrivals—useful if you're deciding whether to wait for workspace-wide AI search before reorganizing notes, or to hold off on mobile-heavy workflows until the iOS app lands.
The rest of the board is dominated by open feature requests (offline mode, version history, Kanban views, table improvements, RTL support and more) that haven't been moved into either column yet. If one of those matters to you, adding your vote or context on Saga Feedback is the practical next step, since prioritization there shapes what moves into Planned next.
How can I vote for or prioritize the features I want most in Saga?
Voting happens on Saga's public feedback board, where each feature request has its own upvote count. Open the request you care about and use its vote control; your vote is what pushes the item up the ranking the Saga team sees. If nothing matches your need, submit a new request so it can start collecting votes.
How to make your votes count
- Search before voting. With around 40 open requests listed, duplicates split support. Search for the outcome you want (for example "offline" or "table") rather than the exact wording you'd use.
- Vote for the problem, not the phrasing. Requests like offline mode, an API, version history and a mobile app each represent a distinct workflow gap; pick the ones that actually block your day-to-day use.
- Use the status labels as a signal. Items marked Planned or In Progress already have momentum. Adding your vote there reinforces existing work; voting on unlabeled requests is how you argue for something new.
- Add context in a comment. A short note on your use case (team size, what you're migrating from, what you do instead today) is more persuasive than a bare upvote.
What the board tells you about priorities
The highest-vote open requests cluster around AI and structure: workspace-wide AI search (38 votes), an iOS app (38), offline mode (48), version history (31) and Kanban views (15). Meanwhile, smaller items like sortable tables, column resizing and comments sit in the single digits. If you run a research or writing workflow, the AI and offline items are the ones worth backing; if you manage projects, the Kanban and task-related requests matter more.
A practical next step: list the three tasks you most often leave Saga to do elsewhere, find the matching request for each, and vote plus comment once. That gives the team a concrete, prioritized signal instead of a scattered set of upvotes.
Does Saga support offline mode or a mobile app?
Yes for mobile, not yet for offline. Saga's public roadmap lists an iOS mobile app as In Progress and offline mode as Planned, so neither is finished today; the iOS app is the nearer of the two.
What that means in practice
- Offline mode (Planned): treat Saga as a connected tool for now. If you work on trains, flights or spotty Wi-Fi, plan to draft in a local document and paste into Saga later, or pick a notes app with proven offline sync for those sessions.
- iOS app (In Progress): in-progress items can slip, so don't commit a team to Saga on the promise of a native app. Ask the Saga team for a target window before you standardize on it; meanwhile, a mobile browser is the usual stopgap, and you should test whether editing feels acceptable on a phone.
Choosing based on your needs
If offline access is a hard requirement — field work, travel-heavy roles, regulated environments — Saga is a poor fit today regardless of the mobile app. If you mainly work online and want phone access for quick capture and reading, the in-progress iOS app is a reasonable bet, but verify its status before rollout.
You can track both items and add your own vote or use case on Saga Feedback, where the roadmap board shows current status. A useful next step: search that board for "offline" and read the comments to see whether the team has described scope or timing, then decide whether to wait or adopt a companion offline tool.
How can I use tables, tasks, and Kanban views together in Saga?
Saga's feedback board shows tables, tasks and Kanban as separate, partly unfinished pieces rather than a fully connected workflow. The board lists Kanban View, Kanban boards for projects, Sortable tables, Status field in Tasks, Tags for Tasks, Add tasks to a collection and View Tasks by Collection as feature requests, with Kanban View and the iOS app marked In Progress. Treat the combination below as a workable pattern to aim for, not a documented Saga feature set.
A practical pattern
- Table as the source of truth. Keep one table per project with a status column (To do / Doing / Done) and a short title column. Tables are where you capture and edit the detail.
- Tasks for the things you actually do. Create a task for each row that needs action, and use the task's status to mirror the table's status column. The requested Status field and task tags would make this less manual; until then, keep task titles prefixed with the project name so they stay findable.
- Kanban as the weekly view. Use a Kanban board grouped by status for standups and planning, and return to the table for editing. The board answers "what's moving?"; the table answers "what exactly is it?"
Who this suits
A solo product person or a small team running one or two projects gets the most from this: a table for scope, tasks for commitments, and a board for a quick status read. Teams needing strict cross-project reporting will feel the gaps — no API and no collection properties are listed as requests, so rollups across collections stay manual.
Decision criteria
Choose Saga for this workflow if your projects fit on one board and you can live with tasks and tables being loosely linked. If you need tables that sort and filter natively, or tasks that roll up by collection, check the roadmap status before committing. For a more mature task-and-board combination, compare with Notion or Linear if your work is primarily engineering issues.
Next step: open the Roadmap board on Saga Feedback and upvote Status field in Tasks and Sortable tables — those two requests do the most to close the gap between the three views.
Amazon Route 53
Google Workspace
User reviews (0)