Papaya Mobile’s Social Splash: HTML5 & Flash Game Integration
Join the DZone community and get the full member experience.Join For Free
hard to get specifics on this, but here’s what i think i’ve found out. papaya mobile , a social game & distribution network, has released a beta of “social splash”.
it allows you to package your html5 or flash games into an apk (an android application). i believe it currently is a browser wrapper, thus using whatever browser is supported on that particular phone. for flash games, this means never targeting any player version about 11.1 since adobe has abandoned flash player for mobile browsers, unless a manufacturer implements a newer flash player version on their particular phone. once approved, papaya will then publish this apk to their gaming market.
first, for all the reach html/js/css has, you aren’t in the mobile markets. this is where people buy apps/games on mobile. this is yet another option for getting into app markets as well as papaya’s translation and market maneuvering/placement features… using html5 or flash games. even if you were to utilize phonegap , they’re just a mobile development & deployment technology, unlike papaya which is a social network + market distribution + translation services.
second, as far as i know, there previously was no way to utilize papaya’s social features such as achievements, scores, chat, leaderboards, and virtual currency unless you coded native android java or objective c ios. even corona sdk only gives you access to the high scores and achievements. now, you can utilize all of them via html5 or flash games. granted, you could use the captive runtime in adobe air to interface their java jar with your flash as another option as a native extension , but papaya has automated it for you.
build your game, test it, and when ready, upload to their site and it’ll make an apk and eventually approve to the market for you. what i haven’t figured out yet is how you actually access these api’s. there’s references to use “askuserinput” for offloading text input to the sdk vs. using built in flash textfields, but i can’t find this in any of the docs i’ve searched. i’ll update this post when i get my hands on some docs/info.
either way, feels very android ish (aka simple git-r-done): upload file on single form == done, which i like. be nice if this supported air eventually, but i reckon they assume you’ll use native extensions, so… maybe it’s already perceived as supported.
Opinions expressed by DZone contributors are their own.