Construct for Playables

C3 is the go to engine for Html5 games, but there's been very little done with it to make Html5 playable ads, and we even have an inline export for them already.

I've been wondering why that is and it occurred to me that while we have the mechanics, we don't have the rest, the parts that advertisers, and networks need to plug our exports in.

This is an unexplored area that many users would like to try not just to make ads for their own games, but as an income opportunity as well. Even more so now that Animate is a thing.

What all do we need to make it viable? Could we start with a plug for MRAID?

iab.com/guidelines/mraid

Could we branch out to the networks and get some input from them?

Forget about the engine - MRAID requires a very small size.

Alas, only HTML5 and JavaScript

Forget about the engine - MRAID requires a very small size.

As far as I can tell MRAID doesn't care, its the network that cares, and its usually 2 to 4 mb, and C3's runtime is freakishly small already.

Alas, only HTML5 and JavaScript

And images, definitely images.

2. no API for the most ad networks

3. Facebook thinks that construct games are a some sort of virus and block it haha

The only feasible way to deal with number 2 is via scripting.

They've stated multiple times they won't make anything for specific third parties.

I would expect that a MRAID plug would handle most of that, but I don't know.

What else do we need?

What else do we need?

we need to change the Playable structure.

For now, playables are saving as one file in base64 format.

it is right for Facebook, but, images and sounds are heavy in the base64 compression.

and facebook is require the main index file as base64 format and folders for resources in zip archive.

so, in theory, if construct could export scripts in base64 with the resources in folders, Facebook will accept the playable. and the size of the playable will be normal, as long as we are excluded resources from base64 compression.

And it is how facebook expected to see the playable.

For now, facebook can't understand the structure of the file and can't load resources

iab.com/wp-content/uploads/2017/07/MRAID_3.0_FINAL.pdf

one file. to be opened in a webview. point to mraid.js (which you will get from the ad sdk). call the different methods, via js

iab.com/wp-content/uploads/2017/07/MRAID_3.0_FINAL.pdf

one file. to be opened in a webview. point to mraid.js (which you will get from the ad sdk). call the different methods, via js

So an MRAID plug would not work?

It seems that multiple methods are being talked about, but not in clear terms.

Is "one file" the inline export?

And then obviously "can't understand structure" has to refer to a zip export.

If it needs to be fixed, we need to identify the export, and what needs to be changed specifically.

i think it should be fairly easy. the events is just js. so you dont need any plugin. the export should be a single html file. and it should import the mraid.js file in the beginning of the html. so this needs to be part of the export. but can be added manually .

For chartboost example the limit is 3mb

answers.chartboost.com/en-us/articles/115001490059

I just created a MRAID using construct and exported as playable ad.

I imported mraid.js and tried a method (open). Worked fine. I see no problem. It rendered correctly as well.

Good news, hope you will share your solution

It is perfectly! Please post an example.

Ok, so again, how do we make playables viable?

A template, or a shareable script would be great, but we also need to get some of the third parties interested.

I'm not sure what you mean? It seems like the C3 'Playable ads' already works fine, I tested in a mraid validator like I shown. also tested now to upload the file to Google, it was recognised and marked as OK)

I don't know which third parties that should be contacted? The ad providers don't care which editor you use to create the html file.

Regarding template it seems like 480x320 is standard (atleast chartboost, digital turbine, Google Ads.). Regarding methods it seems like only mraid.open() is a standard one, which should link to your appstore page and is also recognised as the click event (like cpc charging). As I showed I already verfied this to work fine.

Here is some guidelines:

support.google.com/displayvideo/answer/3208113

developer.digitalturbine.com/hc/en-us/articles/360010946798-MRAID-2-0

answers.chartboost.com/en-us/articles/115001490059

It would be nice if we could get some of them to chime in as to what they prefer, and if they require any other hooks like for api's.