Open HBehrens opened 11 years ago
This should indeed be a part of the coming Developer/
resources for the sake of being able to generate custom schemeApps.json
files with desired filters. The schemeApps.json
is sparse purely for the sake of file size.
I'm a bit busy at the moment, and need to rewrite my scripts as either new Xcode projects or Python scripts.
Regarding the values, I would propose:
Technical
itemId
CFBundleIdentifier
CFBundleVersion
CFBundleExecutable
DTPlatformVersion
MinimumOSVersion
UIDeviceFamily
UIRequiredDeviceCapabilities
CFBundleURLSchemes
Nice-to-have
softwareIcon57x57URL
genreId
artistId
itemName
CFBundleDisplayName
These are the plist keys I used for my very first iHasApp implementation (from the Info.plist
and iTunesMetadata.plist
), which performed scheme + process detection on a version-specific level. The keys may have changed / more added since then.
I will publish a repo with the set of Python scripts I created the recent additions with (as soon as I will find time). After I have puslished those we can discuss how this could be aligned with your idea of the Developer/
resources.
Hey Daniel, you can find the script I was talking about at https://github.com/HBehrens/collectIPAMetaData
I am not sure, if the iHasApp repository is the right place to collect the data I am thinking of, but for offline research (e.g. avoid conflicting URL schemes, find callable apps of a genre) one would need more data than a simple mapping between URL schemes and app ids. Compared to the current
schemeApp.json
there should be a slightly enhanced repository one can eventually derive the simple mapping between URL schemes and app ids from.In addition to these values this list should mirror basic data such as
so even in case an app has been pulled off the app store the willing developer has the chance to detect apps that might be valuable for his purpose and contact the original developer.
What do you think, should this repository be maintained as part of iHasApp? I could also think of another "authority" to collect and maintain this data set. On possible "export" could then be in the format of
schemeApp.json
. But the vast amount of existing mappings are a great start!