Fruitstand: Device Collection

Response from developer

Thanks for your detailed feedback. Regarding having to fill in every attribute on a product page, this is actually not the case. The only attributes that are required for a product are those that are in the “Basics” section (i.e. color, working status, year acquired etc.). All other attributes are completely optional. The “Basics” section has key identifying attributes for a product; however, I can understand that in some cases it may make sense to make some of these optional. As for support for older products and products like the Xserve, these are a bit more of a niche use case. Currently, to add pre-Intel Mac models, you would need to select “Other/Earlier Models” as your Mac model type, and fill in the model name. This is mainly because a suitable icon (consistent with the other products) does not exist for these older products. I can see adding more robust support for older Macs in a future release if there is enough user demand. I hear your requests for new attributes and auto-populating certain attributes for certain products. Currently many of the attributes you describe can be easily added using the custom attributes feature and used across your entire collection automatically. New attributes will be added over time if they make sense for most users. The goal is to have a balance of enough attributes to describe a product, but not too many that most users will be overwhelmed. Custom attributes are there to fill the gaps for users who wish to go further. I agree that certain attributes should be “smarter” or auto-populate; I look forward to adding refinements in future releases. As for actually running the app on older Apple products, this is not something that is feasible from my side. This app is written entirely in Swift and using SwiftUI and modern technologies. To support much older Apple products would mean a near-complete rewrite of the application using legacy APIs and targeting software versions which Apple no longer officially supports.