Hey everyone, Omar here co-founder of Blitzit.
The candid feedback and reviews we've been getting lately means a lot, and I want to address it directly because you deserve that.
A lot of the issues being reported are concentrated on Windows, and I want to give you the full picture of why.
When we started Blitzit, the original MVP had one goal: one click to launch your to-do list panel with a focus timer, starting with macOS only. That version went through a lot of optimisation until the time tracking was essentially fail-proof. As people fell in love with it, we knew we had to grow. So we made a bet: cross-platform from day one. Windows, macOS, iOS, and Android, all at once, right out of the gate, and Electron was the vehicle for that.
What we underestimated was the technical cost. To support every platform talking to each other in real time, we had to build out API endpoints for everything; task ordering, schedules, time estimates, time tracking, system-specific behaviour, so that macOS, Windows, Android, and iOS are always in sync.
A huge amount of the original code had to be rewritten from the ground up to support that architecture. That's also why task reordering on mobile isn't available yet, that endpoint is being finalised and will be releasing very soon.
Part of why Windows has been the most affected is the nature of the platform itself. Unlike macOS, which has controlled and predictable update cycles, Windows pushes frequent core OS updates across an enormous range of hardware configurations and setups. Every one of those updates has the potential to impact how our app behaves, and with Electron as our cross-platform vehicle, Windows absorbs the most unpredictable surface area of any platform we support. It's not an excuse, it's just the reality of building on Windows at this level, and it's something we're actively architecting our way out of. This is why around 30% of Windows users are experiencing ongoing issues, whereas for most macOS users there's barely any issues being reported.
And it's also worth being clear about something. This isn't one codebase. It's four: Electron macOS, Electron Windows, Apple Native, and Android Native. Four separate stacks maintained, updated, and kept in sync by 3 engineers, all part of the founding team. That reality shapes everything about how fast we can move.
Our more mature competitors either started with web (impossible for us as we wanted the blitz panel dynamic window experience) or took years before tackling additional platforms. Superlist ($13m funded), backed by the founder of Wunderlist, did 2 years of private beta and still has no native Windows app today. Raycast (27m euros funded) launched on macOS in 2020 and only entered Windows public beta in November 2025, five years later. Todoist has been in the market since 2007 and TickTick since 2013. Both have had well over a decade to mature their cross-platform infrastructure to where it is today. We tried to do it all from the start, and we're working our way through the challenges of that bet. We are 2 years in challenging ourselves to build to support all 4 platforms, without being web first and with ZERO funding!
All this being said, we live in an age where AI tools can help us move faster, and we're leaning into that. That's also why we've structured the team to work in parallel rather than sequentially.
One engineer is dedicated entirely to integrations. Webhooks has the most votes on our roadmap and for good reason as it solves the integrations problem in one shot, connecting Blitzit to virtually every tool our users already work with. MCP is a natural expansion of that same demand, and yes, we know it's the one that looks like we're chasing shiny objects. We're not. It's a deliberate strategic bet. AI-powered workflows are becoming the standard, and MCP positions Blitzit at the front of that shift. We're building for our users and for where the market is heading at the same time. In a crowded space, staying relevant isn't optional, it's survival.
Our other engineer is focused entirely on stability and re-architecting how we handle cross-platform development, so we're not constantly fighting the same battles. These aren't competing priorities. They're running side by side, every day.
On the nearest roadmap items, we have underestimated our original delivery but here's where the most requested items stand:
Tags — dev started last week.
Webhooks and MCP - already fully tested and ready in test, will be in your hands within 1 to 2 weeks.
Better list navigation — new UI ready in test, coming soon.
Due dates and deadlines — actively in progress.
Task title wrapping — for daily users the first few words have generally been enough, with notes providing deeper context, which is why it got deprioritised. But we hear you and a preference toggle is being planned.
Mobile task reordering — endpoint being finalised, planned for first week of March.
Windows tracking issues - actively being worked on, hard to predict the timeline here as it's been an ongoing issue, we're no longer patching but trying to figure out an architectural fix.
There's a lot more to report on so I'm putting together a behind-the-scenes video so you can see exactly where things stand.
We know we still have work to do, and we're not shying away from that. And I can assure you this team has grown a lot, what's coming reflects that, and we're genuinely excited about where this is heading. Thanks for being part of the journey. 🙏
Hey everyone, Omar here co-founder of Blitzit.
The candid feedback and reviews we've been getting lately means a lot, and I want to address it directly because you deserve that.
A lot of the issues being reported are concentrated on Windows, and I want to give you the full picture of why.
When we started Blitzit, the original MVP had one goal: one click to launch your to-do list panel with a focus timer, starting with macOS only. That version went through a lot of optimisation until the time tracking was essentially fail-proof. As people fell in love with it, we knew we had to grow. So we made a bet: cross-platform from day one. Windows, macOS, iOS, and Android, all at once, right out of the gate, and Electron was the vehicle for that.
What we underestimated was the technical cost. To support every platform talking to each other in real time, we had to build out API endpoints for everything; task ordering, schedules, time estimates, time tracking, system-specific behaviour, so that macOS, Windows, Android, and iOS are always in sync.
A huge amount of the original code had to be rewritten from the ground up to support that architecture. That's also why task reordering on mobile isn't available yet, that endpoint is being finalised and will be releasing very soon.
Part of why Windows has been the most affected is the nature of the platform itself. Unlike macOS, which has controlled and predictable update cycles, Windows pushes frequent core OS updates across an enormous range of hardware configurations and setups. Every one of those updates has the potential to impact how our app behaves, and with Electron as our cross-platform vehicle, Windows absorbs the most unpredictable surface area of any platform we support. It's not an excuse, it's just the reality of building on Windows at this level, and it's something we're actively architecting our way out of. This is why around 30% of Windows users are experiencing ongoing issues, whereas for most macOS users there's barely any issues being reported.
And it's also worth being clear about something. This isn't one codebase. It's four: Electron macOS, Electron Windows, Apple Native, and Android Native. Four separate stacks maintained, updated, and kept in sync by 3 engineers, all part of the founding team. That reality shapes everything about how fast we can move.
Our more mature competitors either started with web (impossible for us as we wanted the blitz panel dynamic window experience) or took years before tackling additional platforms. Superlist ($13m funded), backed by the founder of Wunderlist, did 2 years of private beta and still has no native Windows app today. Raycast (27m euros funded) launched on macOS in 2020 and only entered Windows public beta in November 2025, five years later. Todoist has been in the market since 2007 and TickTick since 2013. Both have had well over a decade to mature their cross-platform infrastructure to where it is today. We tried to do it all from the start, and we're working our way through the challenges of that bet. We are 2 years in challenging ourselves to build to support all 4 platforms, without being web first and with ZERO funding!
All this being said, we live in an age where AI tools can help us move faster, and we're leaning into that. That's also why we've structured the team to work in parallel rather than sequentially.
One engineer is dedicated entirely to integrations. Webhooks has the most votes on our roadmap and for good reason as it solves the integrations problem in one shot, connecting Blitzit to virtually every tool our users already work with. MCP is a natural expansion of that same demand, and yes, we know it's the one that looks like we're chasing shiny objects. We're not. It's a deliberate strategic bet. AI-powered workflows are becoming the standard, and MCP positions Blitzit at the front of that shift. We're building for our users and for where the market is heading at the same time. In a crowded space, staying relevant isn't optional, it's survival.
Our other engineer is focused entirely on stability and re-architecting how we handle cross-platform development, so we're not constantly fighting the same battles. These aren't competing priorities. They're running side by side, every day.
On the nearest roadmap items, we have underestimated our original delivery but here's where the most requested items stand:
Tags — dev started last week.
Webhooks and MCP - already fully tested and ready in test, will be in your hands within 1 to 2 weeks.
Better list navigation — new UI ready in test, coming soon.
Due dates and deadlines — actively in progress.
Task title wrapping — for daily users the first few words have generally been enough, with notes providing deeper context, which is why it got deprioritised. But we hear you and a preference toggle is being planned.
Mobile task reordering — endpoint being finalised, planned for first week of March.
Windows tracking issues - actively being worked on, hard to predict the timeline here as it's been an ongoing issue, we're no longer patching but trying to figure out an architectural fix.
There's a lot more to report on so I'm putting together a behind-the-scenes video so you can see exactly where things stand.
We know we still have work to do, and we're not shying away from that. And I can assure you this team has grown a lot, what's coming reflects that, and we're genuinely excited about where this is heading. Thanks for being part of the journey. 🙏
Hey everyone, Omar here co-founder of Blitzit.
The candid feedback and reviews we've been getting lately means a lot, and I want to address it directly because you deserve that.
A lot of the issues being reported are concentrated on Windows, and I want to give you the full picture of why.
When we started Blitzit, the original MVP had one goal: one click to launch your to-do list panel with a focus timer, starting with macOS only. That version went through a lot of optimisation until the time tracking was essentially fail-proof. As people fell in love with it, we knew we had to grow. So we made a bet: cross-platform from day one. Windows, macOS, iOS, and Android, all at once, right out of the gate, and Electron was the vehicle for that.
What we underestimated was the technical cost. To support every platform talking to each other in real time, we had to build out API endpoints for everything; task ordering, schedules, time estimates, time tracking, system-specific behaviour, so that macOS, Windows, Android, and iOS are always in sync.
A huge amount of the original code had to be rewritten from the ground up to support that architecture. That's also why task reordering on mobile isn't available yet, that endpoint is being finalised and will be releasing very soon.
Part of why Windows has been the most affected is the nature of the platform itself. Unlike macOS, which has controlled and predictable update cycles, Windows pushes frequent core OS updates across an enormous range of hardware configurations and setups. Every one of those updates has the potential to impact how our app behaves, and with Electron as our cross-platform vehicle, Windows absorbs the most unpredictable surface area of any platform we support. It's not an excuse, it's just the reality of building on Windows at this level, and it's something we're actively architecting our way out of. This is why around 30% of Windows users are experiencing ongoing issues, whereas for most macOS users there's barely any issues being reported.
And it's also worth being clear about something. This isn't one codebase. It's four: Electron macOS, Electron Windows, Apple Native, and Android Native. Four separate stacks maintained, updated, and kept in sync by 3 engineers, all part of the founding team. That reality shapes everything about how fast we can move.
Our more mature competitors either started with web (impossible for us as we wanted the blitz panel dynamic window experience) or took years before tackling additional platforms. Superlist ($13m funded), backed by the founder of Wunderlist, did 2 years of private beta and still has no native Windows app today. Raycast (27m euros funded) launched on macOS in 2020 and only entered Windows public beta in November 2025, five years later. Todoist has been in the market since 2007 and TickTick since 2013. Both have had well over a decade to mature their cross-platform infrastructure to where it is today. We tried to do it all from the start, and we're working our way through the challenges of that bet. We are 2 years in challenging ourselves to build to support all 4 platforms, without being web first and with ZERO funding!
All this being said, we live in an age where AI tools can help us move faster, and we're leaning into that. That's also why we've structured the team to work in parallel rather than sequentially.
One engineer is dedicated entirely to integrations. Webhooks has the most votes on our roadmap and for good reason as it solves the integrations problem in one shot, connecting Blitzit to virtually every tool our users already work with. MCP is a natural expansion of that same demand, and yes, we know it's the one that looks like we're chasing shiny objects. We're not. It's a deliberate strategic bet. AI-powered workflows are becoming the standard, and MCP positions Blitzit at the front of that shift. We're building for our users and for where the market is heading at the same time. In a crowded space, staying relevant isn't optional, it's survival.
Our other engineer is focused entirely on stability and re-architecting how we handle cross-platform development, so we're not constantly fighting the same battles. These aren't competing priorities. They're running side by side, every day.
On the nearest roadmap items, we have underestimated our original delivery but here's where the most requested items stand:
Tags — dev started last week.
Webhooks and MCP - already fully tested and ready in test, will be in your hands within 1 to 2 weeks.
Better list navigation — new UI ready in test, coming soon.
Due dates and deadlines — actively in progress.
Task title wrapping — for daily users the first few words have generally been enough, with notes providing deeper context, which is why it got deprioritised. But we hear you and a preference toggle is being planned.
Mobile task reordering — endpoint being finalised, planned for first week of March.
Windows tracking issues - actively being worked on, hard to predict the timeline here as it's been an ongoing issue, we're no longer patching but trying to figure out an architectural fix.
There's a lot more to report on so I'm putting together a behind-the-scenes video so you can see exactly where things stand.
We know we still have work to do, and we're not shying away from that. And I can assure you this team has grown a lot, what's coming reflects that, and we're genuinely excited about where this is heading. Thanks for being part of the journey. 🙏
