Engine Poll Thngy Vote

TTStu

Hi,

Steffen Itterheim is doing some poll (saw it on Twitter) about your preferred rendering engine, and I'm happy to see Sparrow listed up among "the big ones" so I'd like to see it get the votes it deserves!

http://www.webpollgenerator.com/ViewPoll.php?p=528fc819cacaf

Why? Because the more devs that add Sparrow support to their various offerings, the better for Sparrow.

From reading Steffen's random research that he posts, as far as i can see it is cocos2d that has been hit the hardest by Spritekit, and NOT Sparrow by a longshot...

Long live teh Sparrow!

Shilo

It seems Sparrow has two votes now. I assume you and I. Even though the poll is currently at only 53 votes, it's a shame that Sparrow has less votes than all engines, including custom OpenGL engine and "other". It's also surprising to see that Sprite Kit has already become the preferred engine with all its limitations.

TTStu

The good news (in my eyes) is that as far as I can tell, this isn't an inherent Sparrow failing, it is simply 2 things:

1) Visibility... anytime anyone out there on the interwebs asks "what 2d engine should I use for iOS" noone is saying "Sparrow". That is surely because all of us are just not vocal enough.

2) Lack of tutorials, people just wanna be walked through step by step getting up and running. Steffen posted some infographics a week or two ago, and I noted that whilst ALL OTHER engines suffered a drop in searches since the release of SpriteKit, Sparrow searches actually INCREASED.

This was from Stackoverflow. Basically what this means is that increasing numbers of folks are searching stackoverflow for "sparrow tutorial" and finding nothing.

This needs to change 🙂

This is what I break it down to in my head: cocos2d is too complicated, SpriteKit is too limited... ENTER SPARROW!

Also, I am REALLY interested that there have been more than one posts HERE lately from folks who STARTED on Starling, and have migrated to Sparrow. Why would this be? I dunno, 'cos I would have thought it would be the other way around (for cross platform abilities) but it's not the case.

Anyways, some food for thoughts lol.

Daniel

Thanks for posting that link, TTStu! I voted right, away, of course. ;-P

Yes, Sparrow is unfortunately often forgotten when the questions about an ObjC framework comes up. Visibility is our main problem, that's for sure.

E.g. when you look at Starling, which was extremely pushed by Adobe (with blog posts, conference-talks, even a book), it received a lot of popularity much quicker -- even though the APIs are identical! Sparrow, on the other hand, lives just via word of mouth, and via some people who started with Starling and want to go native for one reason or the other.

It's difficult to be the underdog! 😉