Adding applications to AppSnap
February 19, 2008Adding applications to AppSnap takes longer then you would think. Each application needs to be downloaded, installed and then uninstalled in order to get all the information that AppSnap needs. On an average, it takes a good 10-15 minutes per application, excluding any download time. That’s not too bad when you start out but after a point, it is too tedious to deal with.
With 1.3.3, AppSnap crossed the 200 mark in terms of supported applications. It took almost a year and a half to get that far and that reflects the pains associated with growing the database. Considering I am the only guy adding applications as well as enhancing AppSnap, both on a part-time basis, it makes it that much slower. Something had to change.
It is not possible to automate database additions since each application is unique. However, it is possible to speed up the steps that it takes add an application. To make life a little easier, I added the -a flag to the AppSnap CLI to facilitate adding applications. Using -a, it now takes at most five minutes to get an application added to AppSnap (excluding download time). If you haven’t noticed already, the database now has 285 applications and counting. That is more than 80 applications in 12 days. Not bad.
Adding applications is not only faster, but a lot more fun. Indeed, it is the small things that make a big difference.
Hello
I am wondering why you do not make “database creation” a community work.
The Idea:
1. Let AppSnap detect installed applications (search \Program Files, search registry …)
2. When AppSnap “see” an installed application is not in DB, let user tell you more:
The right name of the application
where to download new version/update
ask him/guide him to install/uninstall it by -a flag …
3. let him to upload the information to an “sandbox”
4. make an process of quality assurance (DB testers, cross reference (similar app from various user is more reliable then from one, contributors classification …)
5. push it to the DB
The step 4. is important, you would not like to let users add an syware or viruses.
Hello Petr,
Actually, the ultimate goal is to make it a community driven activity. The database, which was originally an .INI file in SVN has been moved to Zoho Creator so it is now possible to have multiple people add applications as well as give specific people access to manage the database. This is even described on the AppSnap website under the Applications tab. The -a flag was to make adding entries quicker.
At this point, the database is ready to be maintained by anyone who has the skills as well as the interest to do so. Just that I’m yet to hear from anyone who is interested to do so.
Thanks.
Actually the best ppl to maintain the database is the software creators. Make some xml(or something) file format that can contain the information appsnap needs and app creators can put them on their download site. If 10% of the developers does this it will save a lot of time.
On my “round tuit” list is to write a greasemonkey script that will parse an ini section and use it to fill in your app submission form automatically. That would make submitting a little less error-prone, for me at least.
Feel free to google “round tuit” and “greasemonkey firefox”
Actually, the Zoho Creator application has a feature to import multiple rows in CSV format. That’s why I added the -V flag to the AppSnap CLI. It exports the app entry in the appropriate CSV format which I then copy/paste into Zoho Creator.
Unfortunately, this CSV import feature is only accessible to the administrator so if it makes it easier for you, just email the CSV to me and I’ll import it. You can run a command like:-
appsnap -n NewApp1,NewApp2,NewApp3 -V
That will export all your new app entries which I can then copy/paste into Zoho.
Hope that helps.
Thanks.