Hacker News Reader

Comment by jvrossb | Hacker News Reader

Thanks! It occurred to us that had we been reading HN before applying we'd have gotten a little demoralized once we found out that all YC companies had apparently "hacked" their way in with some generally non-reproducible gimmick. We figured we should point out that this probably isn't the case.

View on HN

If you have time, it'd be nice to read a "what we got out of YC, and how it's shaped our path going forward." This would be interesting independent of whether you are still working on the startup you did with YC.

YC changed a lot for us and we're still going strong on the startup we did with YC. Perhaps that'll be next week's blog post :)

EDIT: And it'll be full of more silly things we did that probably didn't matter and that you should also not do.

OT, but if someone publishes though you, and you provide art and music, who owns what? What happens if they want to go cross-platform? Do you sign over the rights (if any) to the art to them? Or will you take royalties off the game if ported to, say, Android? Or will it not be permitted at all?

Simplified, we own the art and music, the developer owns all the code. We get a license to the code and can publish it across multiple platforms, we owe the developer their share no matter what platform their game ends up on. The developer gets a license for our art only valid if published through us. So if the game is ported by us to Android, we still take royalties.

The developer can strip out all of our assets and republish on any platform without giving us a rev share if they want.

Thanks, that answers my questions. I didn't realize you do cross-platform publishing yourself.

We're planning on doing this soon!

Reply on news.ycombinator.com