Return to Answer

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

I'm working on an idea for an app.

In true "customer development" fashion, I'd like to publish the idea, with a screenshot of what it will look like, to see what kind of reaction it gets and what features people want it to have. It's not difficult to implement, but I'd rather not rush into it without having some kind of idea whether anyone is interested.

Is it OK to publish without an implementation, to get a sense of what people expect from my app before the first version?

Answer:

Publish using the (new) placeholder tag.
See "http://stackapps.com/questions/4573/my-app-has-to-be-published-first-but-its-still-under-development".

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

I'm working on an idea for an app.

In true "customer development" fashion, I'd like to publish the idea, with a screenshot of what it will look like, to see what kind of reaction it gets and what features people want it to have. It's not difficult to implement, but I'd rather not rush into it without having some kind of idea whether anyone is interested.

Is it OK to publish without an implementation, to get a sense of what people expect from my app before the first version?

Answer:

Publish using the (new) placeholder tag.
See "https://stackapps.com/questions/4573/my-app-has-to-be-published-first-but-its-still-under-development".

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

I'm working on an idea for an app.

In true "customer development" fashion, I'd like to publish the idea, with a screenshot of what it will look like, to see what kind of reaction it gets and what features people want it to have. It's not difficult to implement, but I'd rather not rush into it without having some kind of idea whether anyone is interested.

Is it OK to publish without an implementation, to get a sense of what people expect from my app before the first version?

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

I'm working on an idea for an app.

In true "customer development" fashion, I'd like to publish the idea, with a screenshot of what it will look like, to see what kind of reaction it gets and what features people want it to have. It's not difficult to implement, but I'd rather not rush into it without having some kind of idea whether anyone is interested.

Is it OK to publish without an implementation, to get a sense of what people expect from my app before the first version?

Answer:

Publish using the (new) placeholder tag.
See "http://stackapps.com/questions/4573/my-app-has-to-be-published-first-but-its-still-under-development".

I'm working on an idea for an app.

In true "customer development" fashion, I'd like to publish the idea, with a screenshot of what it will look like, to see what kind of reaction it gets and what features people want it to have. It's not difficult to implement, but I'd rather not rush into it without having some kind of idea whether anyone is interested.

Is it OK to publish without an implementation, to get a sense of what people expect from my app before the first version?

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

I'm working on an idea for an app.

In true "customer development" fashion, I'd like to publish the idea, with a screenshot of what it will look like, to see what kind of reaction it gets and what features people want it to have. It's not difficult to implement, but I'd rather not rush into it without having some kind of idea whether anyone is interested.

Is it OK to publish without an implementation, to get a sense of what people expect from my app before the first version?