The problem 2048 solves

The game looks deceptively simple to win but starts becoming complex as it goes. So we have given an Undo feature to backtrack your moves and get a second chance at the game without completely losing it.

We seek to gamify the Undo feature to make it more fun by having it work only if you have tokens for it. These tokens will be given to the user based off their last game's score. It will be a cool way to incentive the gameplay to keep the player pushing to 2048 without being overly simple.
This is currently not possible due to the limitations of CelerX SDK.

Challenges we ran into

Celerx JS SDK is available as a "module". Although this makes it easier to be used under modern apps and framework.
It requires specific handling to have the file work in a webpack based system and does not lend itself to be used simply as an imported js file in an HTML file.

The steps demonstrated under the "CelerX Development Tutorial Lesson 1 - Solo Game" video does not work out of box with the latest version of Celerx.
Eg: The video does NOT mention that we need the onStart and ready method to successfully integrate CelerX SDK.
Since this video is mentioned as a quick guide on the Docs, it does not help to its complete potential.
The "celerx-example-go-celer" bears the proper working codebase for the reference application under the "answer" branch but since its not mentioned explicitly anywhere in the docs or in the aforementioned video, testing the reference app took a significant effort.

The deployed Celerx app when being tested does not show the HTML errors out of the box and since this app resides under the Celerx app on the phone, debugging to identify and rectify potential errors is not possible unless Celerx app allows remote debugging.

The non-mention of Cache Propagation Delay for the deployed apps made it difficult to confirm if the new versions of the codebase for the app is being reflected while testing the app on the portal.
The delay being around 5 min on a average also added to the turnaround time for testing newer versions of the code.