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
- name
- bundle id
- version
- developer website
- genre
- supported devices
- keywords
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!
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.jsonthere 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!