{"id":45635,"date":"2024-11-01T16:11:17","date_gmt":"2024-11-01T20:11:17","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=45635"},"modified":"2024-11-04T09:38:10","modified_gmt":"2024-11-04T14:38:10","slug":"fantastical-4-and-windows-version","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/11\/01\/fantastical-4-and-windows-version\/","title":{"rendered":"Fantastical 4 and Windows Version"},"content":{"rendered":"

Flexibits<\/a> (MacRumors<\/a>):<\/p>\n

\n

We’ve spent the last 4 years making Fantastical better than ever across Apple devices, and with version 4.0 we decided to go even bigger by finally bringing the world’s best calendar app to a Windows PC near you.<\/p>\n<\/blockquote>\n\n

For the Mac and iOS versions, it adds a Control Center widget and support for Miro conference calls, but otherwise the release<\/a> notes<\/a> show bug fixes. The price has increased from $40\/year to $57\/year. They are still honoring old, non-subscription purchases with the old feature set.<\/p>\n\n

Flexibits<\/a>:<\/p>\n

\n

The short version is all of the core sync and business logic is shared with Mac (we reuse our Objective-C) and we leverage AppSDK + WinUI for the UI. Currently we don’t make use of Swift on Windows and don’t have plans at the moment to.<\/p>\n<\/blockquote>\n\n

Nicholas Riley<\/a>:<\/p>\n

\n

So far Fantastical for Windows is resource-hungry and unstable, despite its feature completeness. First time I tried to edit an event, it hung. Not sure if this resource usage is typical (memory usage is still climbing, up to about 1.2 GB now) but it’s more than I afford on my work machine, and way more than on the Mac; will try again in a bit I think!<\/p>\n<\/blockquote>\n\n

They’re not using Electron, and it doesn’t seem like there would inherently be a lot of extra overhead from using Objective-C, so hopefully they can get the resource usage down.<\/p>\n\n

Previously:<\/p>\n