[eviks]

Their new version 7 implements the lower quality design of liquid glass while also blocking all ios versions below the latest (so you can't get bug fixes and slow features with the better design). How does that fit the philosophy?

[jxdxbx]

I think it looks better (on Mac and iOS) than any other Liquid Glass app. And I can’t blame Brent for adopting it. One of the standout features of the app is just being native, not trying to re-invent the wheel with custom GUI, and taking advantage of built-in platform features.

My favorite NNW feature is iCloud syncing: Not needing a separate RSS back-end (but of course you can use one if you want to sync with other clients).

[eviks]

> think it looks better (on Mac and iOS) than any other Liquid Glass app

what a weird comparison, the baseline is the previous version of the app

> standout features of the app is just being native, not trying to re-invent the wheel with custom GUI, and taking advantage of built-in platform features

Since the previous GUI isn't custom you don't lose your standout features

[jxdxbx]

Well I think the iOS version is better! I don't like Liquid Glass on Mac though.

[eviks]

Ok, to get back to the original point: does making one of your platforms worse jibe with the quality philosophy?

[jxdxbx]

Yes, because it means that as Liquid Glass improves with Alan Dye out the door, NNW will automatically benefit from the improvements. Having an app that just follows the current standard native platform conventions is better for users and leads to apps that behave in a predicable way.

[eviks]

Doesn't make sense, the improvements can still be worse than pre-glass, and it's not guaranteed they will be better. Also, what's the rush, why not implement it after it's improved? The predictability is the opposite - you've changed design, breaking predictable patterns. Also, cutting off users can't be better for users

[brailsafe]

That's a tough one, but considering it's only the 7th major version to come out in 23 years, I'd say that's a fairly safe place to demarcate backwards compatibility, considering that it's (probably) a fairly major UI overhaul on both iOS and Mac. Despite the poor quality of the OSes themselves, it's just a small studio, gotta pick your battles carefully. You can still use the version you're using, and if you ever upgrade to the new OS you can get the new version, seems reasonable enough to me

[eviks]

> gotta pick your battles carefully

Ok, and how is wasting time making the design worse to follow the OS instead of spending that time implementing missing features a carefully picked battle? I thought the philosophy was prioritizing quality

> You can still use the version you're using

Which would be missing bug fixes and those slow features the may be added next year

[sherry-sherry]

The app has always followed the masOS design language, because the app is built using the native macOS tools. It makes sense for it to match the OS it's on, apps built with stand UI components migrated to 'Liquid glass' much easier.

The app is open source (https://github.com/Ranchero-Software/NetNewsWire), feel free to back-port any features or bug-fixes you would like to spend your time on.

[eviks]

It doesn't make sense because the previous version also matches the OS it's on, liquid glass degradation isn't mandatory and "much easier" is still harder than doing the better nothing.

Your suggestion is just as senseless: among the many things wrong with such a "write the app yourself" approach, you forgot about iOS, even though it's mentioned in the original comment, where you can't freely backport anything due to distribution being locked down

[sherry-sherry]

It makes sense. Like you said, previous versions used the macOS design language at the time, and the current version does the same. The developer has chosen to no longer support older versions of macOS, they aren't required to. The old app still works, and anyone else can work on it if they want.

> you forgot about iOS, even though it's mentioned in the original comment, where you can't freely backport anything due to distribution being locked down

Yes you can. You can create an app today that is compatible with iOS 15.

[eviks]

> You can create an app today that is compatible with iOS 15.

You forgot to address the point, which was about distribution, not creation

The previous paragraph is similarly irrelevant, for example, "aren't required to" - who said anything about requirements??

[busymom0]

Sooner or later, they needed to adopt the Liquid Glass design. While Apple allows developers to temporarily add the UIDesignRequiresCompatibility flag to disable Liquid Glass in current iOS version, they are very clear that that flag is temporary and will go away next version. So they had to adopt it either now or next year even if they didn't want it.

https://developer.apple.com/documentation/BundleResources/In...

> Temporarily use this key while reviewing and refining your app’s UI for the design in the latest SDKs

[eviks]

> sooner or later ... design in the latest SDKs

Or don't use the latest SDK and don't be forced "next year", but continue for many more years. Also "later" is definitely better in such cases because there is some change the design will be improved. Either way, there is no good reason to rush to be worse and cut off users if you proclaim you're into quality