4

I finally stopped stagnating long enough to start working on an application for Stack Apps using the API. Development is going well and within the next 6 to 8 weeks there will be enough functionality for the application to be usable.

I am hoping to be able release the application using a release early/release often methodology, however after a quick chat with Rebecca and reading How to list your app I need some clarification on Jeff's comment:

Remember, you should only publicize your app if it can actually be used!

Effectively I would like to add my application to Stack Apps, and for the initial Alpha/Beta release have users email me requesting access to the application, allowing for a controlled environment of testing before throwing the application out to the world.

Would this be acceptable within the Stack Apps listing, or should I only list the application here once it is available for download by everyone? Alternatively, what would be the best way to get users testing a new Stack Apps application?

Improve this question
2
  • It's pretty much fine to list it now. I've had mine listed for ages and its not released. Stack apps isn't a active site concerning new "questions" so it's not like it would "get in the way". Just tag the question as "apps" not as "app" (until it is released, then you remove the s)
    – Jonathan.
    Commented Jan 25, 2011 at 21:31
  • 2
    I don't read Jeff's comment as "bug-free" or "feature-complete" just "(unqualified) usable".
    – Dennis Williamson
    Commented Jan 25, 2011 at 21:54

1 Answer 1

Reset to default
5

It is acceptable, so long as it is usable in some form.

What we object to is people listing an that exists only in their imagination and not reality. That's not helping people looking for, y'know, actual apps that run on our API...

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .