Closed neymarsabin closed 5 months ago
as the list increases we might find apps which is available in website, desktop software, android and iOS apps, so i think it would be better to list it in tabular form 'N/A' to indicate the program is unavailable in given platform.
Software Name | Description | Website | Desktop Software | Android App | iOS App |
---|---|---|---|---|---|
Example Money App | A finance management app for personal budgets | Link | Link | Link | N/A |
Software Name | Description | Website | Desktop Software | Android App | iOS App |
---|---|---|---|---|---|
Example Accounting | Accounting software for small businesses | Link | N/A | Link | Link |
Software Name | Description | Website | Desktop Software | Android App | iOS App |
---|---|---|---|---|---|
Example Audiobook | Audiobook player with various features | N/A | Link | Link | N/A |
Software Name | Description | Website | Desktop Software | Android App | iOS App |
---|---|---|---|---|---|
Example News App | App for reading latest news articles | N/A | N/A | Link | Link |
Software Name | Description | Website | Desktop Software | Android App | iOS App |
---|---|---|---|---|---|
Example Ecommerce | Ecommerce platform for small businesses | Link | Link | N/A | N/A |
Thanks @skyGtm, this is a good idea. Also, keep in mind that we will be building a JSON server based on the list here. Anything that favors both will work for me.
instead of editing markdown file, i think it would be better we start listing apps in YAML file(instead of .md file because new contributers who have no knowledge of .md file can easily read YAML and populate respective fields), then we can write python script to parse YAML and generate JSON file and markdown file for easy viewing. This python script can be set to run after merging pull request, via Github CI
YAML is not a good choice here. I don't think people who know YAML wouldn't know JSON. Let's not worry about people not knowing JSON and I believe this is not a problem. Let tell you what I am thinking:
Build a JSON array to build the list. We will have a process that can read JSON pipe the output to markdown as well as serve the JSON array. The benefit of doing this is we can build a monorepo to serve the client too.
We might need to add tags to each URLs to identify them as either mobile/desktop/web apps or combination of them. something like this:-