Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

For software products, it's pretty hard for them to tell the difference between a simulation/rendering and the real thing. If I show a finished UI, it will appear to be fully functional and polished, but there may not be any back-end at all. I often create a fake persistence layer to allow for faster development of the UI. How would they be able to tell the difference? And it's actually not violating the rules at all right?


The simulation/rendering rule is only for "Hardware and Product Design Projects", not software.


I also think that delivered software is a product. I doubt kickstarter would allow SaaS at all (it would be interesting to see what kind of products get rejected during the submission reviews).


Are you sure? Software could conceivably fall under "Product".


Everything on the site could conceivably fall into "Product".

It seems fairly clear to me that they are just trying to prevent these kind of shenanigans: http://blogs.reuters.com/felix-salmon/files/2012/09/bulbs.jp...

http://blogs.reuters.com/felix-salmon/2012/09/18/kickstarter...


There are a bunch of obvious technical mistakes in that, not least of which is that you're not effectively buying a WeMo and getting the bulb for free; only the more expensive master bulb will have WiFi support and the rest will talk to it over much cheaper 802.15.4 mesh networking.


From the comments in the linked blog, there was this comment "The new guideline prohibiting renderings applies only to projects categorized as Product Design or Hardware. Other categories, including Games, are not affected."

which came from Kickstarter's community manager.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: