Oh, sorry about that!

Hopefully you give it a try when you update eventually :)

I will. Thank you for doing a great job anyway. I don't actually feel angry or demand anything from you, although I might sound this way. I just expressed my thoughts which many people obviously share.

May I, however, ask if there is a serious reason to require Big Sur instead of supporting Catalina, Mojave and High Sierra also? I understand you probably don't want to waste resources on actually supporting them but perhaps you could just build against them and let users use it on their own risk?

We're using SwiftUI and WebKit features that were added quite recently (MacOS doesn't get nearly as much love from Apple as iOS). This keeps our product iteration cycle quite high, and the worry is having to implement cumbersome solutions if supporting previous OSs.

I'll have to look into it again to see if I can go back just a bit maybe and assess how much time it would take to support those versions.

We're a pretty small team :)

I would have lobed to try this out as well, but I'm stuck in 32 bit land for the foreseeable future - so I am staying with Mojave.

Ah, what a shame. Hopefully I figure out a workaround to support Mojave :D

I see. Thank you for your time.

Changed the title!

I can speculate this can actually attract even more of the target audience to you. Mac people probably feel more enthusiastic about Mac-specific software announcements and are steadier to go and take a look at something Mac-specific than at yet another generic browser. And for the conversion rate - this probably even is a serious boost.

We have been getting slightly more constructive comments since changing the title, so thanks :D

And those enthusiastic about Mac, also care about things like how 'macOS' is written. Attention to detail matters and shows your own level of dilligence.

Interesting. I typically write it as macOS in conversation, but wasn't aware it was seen as correct to capitalise the M.

Thanks!