On to the discussion on what could make it better or worse… Since I am the developer of repo.sc, I am going to be a bit biased, but I’ll try to be fair

To start off, I’ll list what I think my site is better on:
1) I retain exact structure of the Installer source from the original source. End users get exactly what was delivered by the original source. As such, things are still organized in their original categories. With iAppCat, they’re consolidated into one category. Personally, I think this makes navigation, searching, and working on the Installer part much easier. It also reduces the risk of a bad Installer source due to bad “edits”. I actually sat down and worked out some neat little algorithm with Saurik (Java dev) and Ste (Ste Packaging) to make sure that I deliver the source to you in its latest and most accurate form, so the only error that can possibly occur is if the source is originally error’ing (or you’re using an incompatiable firmware version).

2) The personalized repo link from iAppCat is rather long… it is iappcat.com/r/userid where as my links are much shorter: repo.sc/username (unless you have a very long username that you’re not already fond of typing on your iPod/iPhone). Not a whole lot more can be said about this as it is a one off thing, and can even be done via payload in JailBreaking process.

3) Ability to add multiple packages quickly. Due to popular request, I added the “Add / Remove All” feature for categories. This adds everything from that category at the time for you automatically. So for big categories like games, you don’t need to click 100 times to add all of them. iAppCat, last I checked, does not offer this, and requires multiple clicks to add the packages. This can make setup process require much much more time to complete… But it is a one off kind of thing unless you’re adding and removing things non-stop

4) Package recommendation, and community descriptions. I’ve been putting this one on back burner due to my graduation project for university, but it will be completed in the weeks to come after next week (when I’m done with school for good). A new feature I’m implementing is community descriptions and package recommendations for individual packages. This will allow users to comment and rate packages, so people knows what package does what, and what not. If you’re very lost and confused about the description I just wrote, check out this dummy page that I’ve built to express the idea: http://static.touchtoolset.com/MockUp_Details2.htm

There will also be other social / recommendation type of things to be added, but information on those aren’t made available to public just yet because they’re not quite ready yet

Now, pro’s of their service:
1) Ability to browse at a source level. When I designed repo source, it is designed in such a way so that the end user can “forget about the sources”. I only keep track of the latest version of the software in the database, and allow the system to “forget” older packages from different sources. This is done so that there won’t be duplicate entries in the system (IE: search > psx4all, and you might find tons of kiddie googlepage sources hosting the package because appearently it is cool to steal), and end users don’t accidentally select two of the same packages, and in turn create an endless update loop in Installer. Though, I must say, to be able to browse by source is pretty darn cool. Unfortunately, due to my system design, I don’t think I can implement something like that any time too soon.

2) Ability to add sources to their system automatically. I do it manually here, and only approve things that will work stable, or have been known to be around for some time. Beta and unstable ones are often omitted to prevent problem like the random 13 yr old thinking it is cool to delete files with Installer. It also prevents things like people not respecting private beta rules and share zodttd’s private beta repo. This is a trade off which is not that great… but I guess its a different point of view; I respect developers, so they continue to develop adds, where as iAppCat gives more options to the users, so they can have things they want in one centralized place.

3) A good looking web page. Let’s be honest here, I am a geek; I can’t draw stickman even if my life depends on it. As such, I’m rocking the default vBulletin skin. On the other hand, iAppCat dev is awesome, and created a simplistic yet clean design. If you’re big on visual appeals, here’s the big one for ya.

With that said, I’d say both are pretty cool services. But since I’m developer of Repo Source, I’m biased, and I like my service better. At end of the day, both sites make Installer run faster, and there’s not a whole lot of difference between them. And sorry for the wall of text I’ve created

http://www.iappcat.com/r/5445

and gona show a new Categorie +Segal

Thank you,

Question! Will it keep track of my apps so if there is a newer one that comes out (upgrade) will it notify me?

Not trying to be sarcastic; but does the repo.sc have more sources to search for apps from? or does it load faster?

I’m just trying to figure it out; because I haven’t heard of this other personal repo option, but I can’t really think of what would make one better than the other.