Product roadmap update

We had been being quiet for a while since this forum is open.
And now we believe it's time for us to share some updates regarding the roadmap.

Currently we are mainly working on 2 targets: Android Oreo support and iOS11 support.
There are several phases internally, Oreo compatibility will be the first priority, then is the iOS 11.
For Android, one notable item in our list is Clang support.
For iOS11, new APIs and iPhoneX resolution are the major topics.
Schedule-wise we are aiming early summer 2018 to roll these new platform supports out.

Please notice that these updates are not part of the Bridging License.
We will have a new license pricing model, details will be announced next year.

There will be some news update from now on once in a while regarding the progress of the development, please stay tuned.

Marmalade Team Japan

Have more questions? Submit a request

3 Comments

  • 0
    Avatar
    Michael

    Sorry if this sounds a bit negative but seriously, is that what you aim to do to keep existing customers (let alone find new ones)?

    Just a bit of OS maintenance as a new paid release, i.e. not even covered by those who already paid you, about 1.5 years after the original Marmalade shutdown (I know you got the license a few months later, but it's what it feels like to existing or previous longtime users)?

    I was in kind of a hibernation with some big project that used Marmalade while working on other smaller titles using other middlewares made for rapid development (but at a huge performance cost) but this announcement is not even what the pessimistic me hoped for.

  • 0
    Avatar
    Marmalade Team Japan

    We believe that following up the Android and iOS support is having a very high priority among other topics, to keep Marmalade SDK alive. And that's also what we heard from many existing developers.

    Do you mind if we send you emails to communicate on what you are expecting for?

  • 0
    Avatar
    Andrew Hersee

    Note that the existing license runs full screen on an iPhone X in debug builds by modifying the xCode project. Why do we have to wait till mid 2018 for this support  in release builds? It's not acceptable. I find it exceptionally hard trying to explain to customers why our app does not support full screen on iPhone X and to tell them not to expect it until summer 2018! That makes us look like a very slow company and forces us to try to find alternatives, what are you playing at? Is there no hope for iPhone X full screen support in the next few weeks? Rather than in half a year?

Please sign in to leave a comment.