Feedback
Changelog

Have something to say?

Tell us how we could make the product more useful to you.

Can we have a better zoomed in version on mobile and please make the font in any thing we add lower so the colored box doesn’t cut off weirdly

On mobile I shouldn’t have to see super tiny text on my calendar. It should be able to zoom in and see it closer up. On both mobile and desktop, the font on anything in the calendar has not enough space at the top around the colored box. You should center it more so the colored box has more space.

Matt 6 days ago

1

Restore Default-Based Meeting Creation in AKI Assistant

Problem Previously, the assistant handled lightweight scheduling extremely well. A simple command like “book me a meeting at 7 PM tomorrow” would automatically create a one-hour calendar event with a generic title (e.g., “Meeting”), without asking follow-up questions. This made voice-based scheduling fast and frictionless. Currently, the assistant asks multiple clarification questions before creating the invite (event title, end time, etc.). This introduces unnecessary back-and-forth and significantly reduces the value of using the assistant for quick, hands-free actions. Why this matters The core reason I use the assistant is speed and convenience. In most cases: If I want a generic meeting, I expect sensible defaults to be applied If I need something specific, I’ll provide those details upfront The current flow feels more manual than assistive and breaks the “just say it and it’s done” experience that worked so well before. Requested behavior Please consider restoring (or adding an option for) default-based meeting creation where: Missing details are auto-filled with reasonable defaults (e.g., 1-hour duration, generic title) The meeting is created immediately unless clarification is strictly required This would bring back a much smoother and more intuitive experience, especially for voice commands.

Saran 15 days ago

3

Projects descriptions for better AI tagging

The auto-tagging of my tasks is not working super well, having a way to define rules / some description per project would be a great way to help the LLM identify which project to tag. E.g. project “engineering improvements” I could put some examples (“find better way to do XY”,”prepare OKR process” or similar) or hints on when to apply this.

Alex Prams 15 days ago

2

OVERLAPPING TASKS VISUAL INCONSISTENCY

When I have overlapping tasks on my time grid, there seems to be visual unpredictability—sometimes I can clearly see the overlap, with them side by side, while other times one appears on top of the other. I fear that the latter may affect the observability of some tasks. Please fix this and make it stable. I would rather the overlap be apparent.

Clarence Mungai 17 days ago

4

when updating availabilities in "shared availabilities", the availabilities I previously recorded "hide" my calendar.

For instance, I thought I was available on Friday in the morning. I added a meeting via Google Calendar from 10 to 11 am. I want to update my availabities. The whole Friday morning is “covered” so I have to delete the whole availabity slot, then recreate it again. Maybe some kind of transparency would help

Julie Baillon 19 days ago

3

Add Microsoft Teams as a Conference Tool

Many businesses operate fully within the Microsoft ecosystem and rely on Microsoft Teams as their primary conference tool. Adding native support for Microsoft Teams, alongside Google Meet and Zoom, would make Akiflow more flexible for teams that schedule and run meetings through Outlook and Microsoft 365. This would reduce friction for users who do not use Google based tools and allow Akiflow to better support mixed or Microsoft first environments. This is not about replacing existing options, but expanding compatibility so Akiflow fits more real world business workflows.

Luis Garcia 22 days ago

1

Privacy settings at integration-level: control calendar visibility of task details (Gmail/Slack vs Jira)

Add an integration-level setting that controls whether tasks from that integration show full details when scheduled on the calendar. Problem Some sources are inherently sensitive (Gmail, Slack). Others are usually safe to show (Jira, ClickUp). When a task is placed on the calendar, the event title/notes can expose private content in shared calendars, screen shares, or when someone glances at your calendar. What I would want Per integration (and ideally per calendar), configure the default calendar rendering: Show full details: task title + description/link Redact details: generic title like “Task” / “Focus block” and keep details only inside Akiflow Optional: allow only the source name (e.g., “Email task”, “Slack task”, “Jira task”) Optional: include a private link back to Akiflow without exposing content in the calendar title Example defaults Gmail/Slack: redacted by default Jira/ClickUp: full details by default Why Prevents leaking sensitive info while keeping the workflow intact Makes it safe to use Akiflow scheduling with shared calendars and across devices

Jesse Cok 22 days ago

1

Separation of Personal vs Work tasks

Add a clear Personal vs Work separation throughout Akiflow. Can be as simple as a filter + some todo → calendar settings/routing. What I would like: A dedicated field (or mode) that marks every task as Personal or Work System-wide filtering and views based on that (inbox, lists, search, planner, shortcuts, stats, notifications) Default rules for new tasks (based on source, calendar, project, or manual toggle) Calendar behavior When I schedule a Personal task, it should go onto my personal calendar When I schedule a Work task, it should go onto my work calendar If I change the task type later, Akiflow should move the calendar event to the correct calendar (or at least prompt to do so) Why Keeps work/personal mentally separated and reduces planning clutter Makes shared calendars and scheduling cleaner (especially when you have multiple calendars connected) Removes manual overhead of constantly choosing the right calendar for time blocks Avoids my boss from seeing when I do laundry ;)

Jesse Cok 22 days ago

2

Map source tool priorities to Akiflow task priorities

Add priority mapping in integrations so task priority from source tools carries over into Akiflow priorities. Example (Jira) A Jira issue with the highest priority should automatically become an Akiflow task with the highest priority. If the Jira priority changes (High → Medium), the Akiflow task priority should update accordingly. What’s needed Per-integration priority mapping (Jira, Clickup, etc.) to Akiflow’s priority levels Clear defaults + ability to customize mapping (since tools use different priority schemes) Optional one-way or two-way sync (at least source → Akiflow) Why Priority is core context for planning. Without mapping, imported tasks lose urgency and require manual re-triage in Akiflow.

Jesse Cok 22 days ago

1

UI polish: the product works great, but it looks and feels unfinished (desktop + mobile)

Akiflow solves two major things for me really well: Collecting todos from a wide variety of sources with minimal effort Simple planning views that actually work (Today, This week, This month, etc.) That’s why I’m still trialing it, and being invested in the community here. But the interface doesn’t feel polished or consistent, and it makes the product feel less mature. This isn’t a feature request, it’s a product quality improvement request. While I’m here: the “collecting from sources” part also has real reliability issues around status syncing. Examples: A bookmarked Slack message becomes a todo, but when I mark it done in Akiflow, the Slack message stays bookmarked. Same pattern for emails Jira tickets import correctly when assigned to me (as configured), but when I reassign the ticket to someone else in Jira, the todo stays in Akiflow instead of being removed. What I mean by “unpolished” Visual hierarchy feels messy in places (spacing, typography, alignment) Color palette, shadow usage Components and states don’t always feel consistent Icons Contrasts Some screens feel patched together rather than one coherent system Mobile matters too. A lot. Regardless of device or OS (desktop, iOS, Android, web), it should feel equally polished and consistent. Right now the differences between devices make it feel unfinished. Why this matters It affects trust: the app works, but the UI makes it feel less premium It adds friction and cognitive load when you use it daily It can block adoption because first impressions matter I’m not trying to be an ass here. I know design is subjective (it also doesn’t help that I also work in that field). But this is just my two cents. 🫶

Jesse Cok 22 days ago

1

Assign todos to meetings

Add a way to attach real todos to a calendar event, so tasks can explicitly “belong to” a meeting. Use case In our company we have dedicated weekly 1:1 Slack channels (example: #weekly-manager-employee). During the week we dump things that should be handled in the next meeting. Today I import those into Akiflow via bookmark import, but then they float as normal tasks. I want to drag/link those tasks into the meeting itself so they’re clearly tied to that specific event. What it should do Each event can contain a “Todos for this meeting” list Add existing todos by drag-and-drop into the event, or create new todos from within the event Link, don’t duplicate: the same todo keeps its identity, status, comments, due date, etc. Option to show these meeting-linked todos in the global task view (with a “linked to meeting X” reference) Recurring meetings: todos can be linked to a specific occurrence (not just the series) Why Makes it trivial to collect and process todos that are meant to be handled during a meeting Removes the need to use email/Slack threads as the “meeting todo system” Keeps tasks organized by the meeting they depend on without losing them in the general backlog

Jesse Cok 22 days ago

1

Calendar Activity Feed for all calendars (invite responses + event change log)

Add an Activity Feed that logs calendar activity across all calendars I have access to, including shared family/team calendars. The feed should show who did what and when, so calendar “activity” doesn’t live in email. What it should capture: Invite responses: accepted, declined, tentative, needs action Event changes with attribution: time changes duration changes location / video link changes title / description edits attendee list changes recurrence rule updates cancellations / deletions organizer changes (if applicable) New invites received / sent Why: Today you have to rely on email threads to track responses and edits. Especially valuable with shared calendars (family) where you want a quick “what changed” overview without opening each event. Nice-to-have: Filters (calendar, person, change type, date range) Click-through to the event “Before vs after” diff for changed fields

Jesse Cok 22 days ago

1

Travel time

I’d love to see travel time automation in Akiflow, similar to what Apple Calendar offers. The main value for me is that it removes the manual step of looking up how long travel will take and deciding how much buffer to block. Here’s how I imagine it could work: When adding travel time to an event, Akiflow could try to prefill the “From” location by using the location of the event right before it (as a best guess for where you’ll be). And of course, it would still be possible to override that manually. It would be great if it supports multiple transportation modes, like walking, cycling, public transit, and car. On the calendar side, two things would be especially helpful: In Akiflow itself, travel time could show up as a visually distinct block from the actual meeting (so it’s immediately clear what’s travel vs the event). In other calendars like Google Calendar, it could be created as a real event called “Travel time”, so it blocks availability there as well and nobody schedule over it. One extra idea that would feel really smart: Closer to the meeting (actually probably various checks as you need to be informed earlier when the travel time is longer compared to when it's shorter), Akiflow could re-check whether the estimated travel time still looks accurate (traffic, weather, delays), adjust the travel time automatically and warn you about the changes so you're aware. Also, if the event before it changes (duration or location), it would be great if travel time gets recalculated as well, since that can directly affect where you’re leaving from and when. And a couple of thoughts where Akiflow could potentially differentiate from Apple: Travel time after the event too, not just before (getting back matters as well, depending on the situation). Walking as a transportation method would be amazing (already mentioned above, but calling it out as a differentiator). If you make it so that it's flexible/non-mandatory/and easily overridden, it would be super flexible. Would love to see this.

Jesse Cok 22 days ago

17

Share Availability: Resizable vertical divider for viewing full slot titles

In the 'Share Availability' view, the vertical divider line between the calendar and the right panel cannot be dragged/resized. This causes recurring slot titles to be partially hidden, which is inconvenient for power users who frequently use this feature. It would be great to add the ability to resize this divider or make the right column wider, so that full slot titles are visible. This would significantly improve usability for users who rely heavily on this feature.

Erik Zwep 22 days ago

5