[Testing] Cynagen:
According to this video article posted, I am duplicating efforts already exerted by another. Rather than cut into his efforts to fulfill this, and try to compete with an already existing and established product, this project has been discontinued.

That's good. And you could have sent me a PM directly. Since it's out in the open now, I figured I'd break down the App Portal and how I envision seeing it work once it's finished:

In order to complete account setup on the App Portal, you must provide your XDA-Developers forum username (so we can send you notices for things). This will allow us to tightly integrate the AP with XDA as it's parent.

For everyone:

You each have a score, for testers, just a test score, for developers, a developer score (and if you participate in testing, a testing score as well). These scores will be used to give your projects priorities as well as people priorities for joining tests. This will allow for the best testers to be able to participate where they choose because they provide valuable feedback and otherwise participate frequently (seating for each public project is still first come first serve). For developers this will mean they get the best testers available for their private projects, and should they be active developers too by responding to feature requests in a timely manner as well as the cumulative activity of their projects (updates to the project, new beta code test uploads/etc) will mean they become more prevalent as well for both private and public projects. The scoring system should allow for an extremely active tester and/or developer to quickly become recognized for their contributions and provide them greater opportunities to participate, and leave the occasional tester with a lower score presenting them with projects they may be interested in that still have open seating.

For testers:

Once you sign up (and verify your account with the link PM'd to you to verify your XDA username), you'll be presented with the public beta projects that developers have posted for people with compatible devices compared to the devices you have registered on your account (this will remain an 'honor system' for now as I cannot verify any of this information).

Testers will also be able to opt-in for private (read: NDA) alpha/beta invites, for when a Dev creates a new project on the AP, they can choose to have it private. Anyone with a compatible device that has opted into the private service will receive an invite via PM to join the test pool for private projects should their tester score be high.

Testers will be periodically PM'd with links that take them back to the AP to provide a review of the applications they are testing and provide the developer with anonymous feedback. Repeated failures to submit reviews of the applications you are testing will lower your tester score (and possibly get you removed from the project altogether), thus making you less likely to be invited to any private projects.

For developers:

You do the same sign up (and verification of XDA username), you'll be able to post a project which you are working on almost immediately.

Upon creating a project, you can select your device pool, the maximum number of testers you wish to have participating, and whether the project is public or private. Should you select private, it will not be listed on the website and will send private invites to people with qualifying devices until the maximum number of testers has been reached. BE AWARE: Private application tests do NOT shield your XDA username from testers, don't think this makes the entire thing anonymous, only the testers are!

You will be able to customize some of your questions for the reviews that are being sent out, nothing personally identifiable shall be requested.

Should you experience trouble with any individual user, you will be able to remove them from your test, causing them to lose a number of points comparative to your developer ranking points. Further, when you receive helpful feedback, you will be able to award extra points to the tester for the valuable assistance.

The greater the interaction between developers and testers, the higher everyone's rankings go, this way we can keep an eye on ineffective testers and restrict them, and award the helpful and active testers with more testing opportunities. There will be report buttons/links everywhere so as we define the rules and regulations, we can quickly catch and correct for misbehavior using something that is otherwise supposed to be supremely helpful!