Tim, as John said, Cocos2D is a great framework, and if you like it, there’s of course no reason to switch. But IMHO, choice is always a good thing — and the philosophy behind Sparrow is a little different, which will make it a good choice for many developers.

Sparrow contains everything you need for most games. We will of course add more features like particle systems, etc., and work on performance enhancements — but the target will always be to keep it as lightweight and clean as possible. We’re with Antoine de Saint-Exupéry here:

“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.”

Thus, you will never find a physics engine being a part of Sparrow — there are other libraries that do that far better as we ever could. Instead, we will make it as easy as possible to have our users integrate those other libraries, and create tutorials and articles on our page that help our users get started.

I hope this answers your question =)

Tim, as John said, Cocos2D is a great framework, and if you like it, there’s of course no reason to switch. But IMHO, choice is always a good thing — and the philosophy behind Sparrow is a little different, which will make it a good choice for many developers.

Sparrow contains everything you need for most games. We will of course add more features like particle systems, etc., and work on performance enhancements — but the target will always be to keep it as lightweight and clean as possible. We’re with Antoine de Saint-Exupéry here:

“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.”

Thus, you will never find a physics engine being a part of Sparrow — there are other libraries that do that far better as we ever could. Instead, we will make it as easy as possible to have our users integrate those other libraries, and create tutorials and articles on our page that help our users get started.

I hope this answers your question =)

Tim, as John said, Cocos2D is a great framework, and if you like it, there’s of course no reason to switch. But IMHO, choice is always a good thing — and the philosophy behind Sparrow is a little different, which will make it a good choice for many developers.

Sparrow contains everything you need for most games. We will of course add more features like particle systems, etc., and work on performance enhancements — but the target will always be to keep it as lightweight and clean as possible. We’re with Antoine de Saint-Exupéry here:

“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.”

Thus, you will never find a physics engine being a part of Sparrow — there are other libraries that do that far better as we ever could. Instead, we will make it as easy as possible to have our users integrate those other libraries, and create tutorials and articles on our page that help our users get started.

I hope this answers your question =)

While there are similarities, much is different. As they say this is more geared towards people with Flash/Flex, .Net and Java experience while Cocos2D iPhone is a port of the original Cocos2D project which was originally geared towards those who had used the original Cocos2D framework in Python.

While there are similarities, much is different. As they say this is more geared towards people with Flash/Flex, .Net and Java experience while Cocos2D iPhone is a port of the original Cocos2D project which was originally geared towards those who had used the original Cocos2D framework in Python.

While there are similarities, much is different. As they say this is more geared towards people with Flash/Flex, .Net and Java experience while Cocos2D iPhone is a port of the original Cocos2D project which was originally geared towards those who had used the original Cocos2D framework in Python.