Bugs that will be fixed with iOS 15/macOS 12

[supergeorg]

This issue is used to track bugs that I am unable to fix with reasonable effort and "just work" on the announced iOS 15/macOS 12 Monterey. As soon as these updates release, I will raise the required OS version to them. I am sorry for the users, but (nearly?) all iOS 14 devices support iOS 15 and most macOS 11 devices support macOS 12, so no reason to not use the bugfixes and new features available.
So the "old" iOS 14 version will not receive any new UI, only bugfixes and backend changes, while I work on the iOS 15 version.

• Icon for consume is fork.knife instead of a tuningfork
• Stock: after one interaction icon is clicked, users have to scroll to be able to click another. This gets fixed.
• Stock macOS: The shitty homebuilt Stock grid view gets replaced with a proper table, allowing for much better interaction and way higher performance
• Search: is now natively supported on iOS and macOS, making the design and use much better
• replace URLImage library with native AsyncImage, make usage more widespread
• Add pull to refresh, removing the refresh buttons (bad design)
• Rewrite Web requests to async await, making code easier than completion handlers
• Add swipe actions for shopping list and other quick actions
• Better date formatting
• Better keyboard interaction with onSubmit and supplements for faster data entry
• Better Text field with focused modifier
• Better context menus in stock
• much more

[OmgImAlexis]

• Add pull to refresh, removing the refresh buttons (bad design)

For Mac this should really stay as a refresh button. It feels counter intuitive as a user to pull on a trackpad/mouse device.

[supergeorg]

For Mac this should really stay as a refresh button. It feels counter intuitive as a user to pull on a trackpad/mouse device.

Since I haven't installed the Monterey Beta yet, I don't know how it will look on macOS. I guess it will follow good design principles, but if it isn't good, the button will of course be back on macOS.

[OmgImAlexis]

all iOS 14 devices support iOS 15

One issue you're going hit is jailbroken users. A LOT are still on 14.x or 13.x

Edit: Looking into it iPhone 6 and iPhone 6s both have bugs in iOS 15 to the point where people are seeing complete OS crashes. Granted this is in the beta but I wouldn't be too hopeful for the older devices here.

This means you're only able to support iPhone 7 - 12. Might be worth adding a compatibility chart in the README?

[supergeorg]

I added some compatibility information to the readme. I am sure that Apple will fix the crashes, it is still some months to release.
Concerning iOS 13.x, this OS is unsupported and never will be, since I would have to drop several things, like the shared macOS App.
Also I have no incentive to build an inferior app, just to support some users who don't run a new iOS version. This creates unclean code and hackish workarounds, which are time-consuming. This is the problem with SwiftUI, to get the newest features, you have to drop older versions. Android has a compatibility layer to tackle this problem (AndroidX), but unless something like this is implemented (unlikely, since they support their devices for quite some time), this seems like the best way.
The goal is to provide most users (80% had iOS 14 at the beginning of the year) the best experience possible. This will be the same with iOS 15.