Discontinue of Marmalade SDK

To all Marmalade Developers,
 
We've made a difficult decision, to stop further investment to Marmalade SDK.
 
We know you are going to ask why. So here's the story behind.
The major reason is, we are not able to have Marmalade SDK as a sustainable business.
We used to believe Marmalade SDK is superior in performance comparing to Unity, and we also believe Marmalade provides better mobile platform support comparing to Unreal Engine. However, the world changed in a tremendous speed. Unity addressed it's performance issue within latest releases, on the other hand Unreal Engine also did a great job supporting modern mobile platform. It's a never ending arm race.
 
Recently, we are struggling with iOS. As you all know, Apple changed the policy 2 times in Q1. We were swamped. We had no choice to stop all the task related to iOS 11 to solve the issues, as a result the schedule is hugely delayed. And as you all know, Apple might change it's policy anytime. WWDC is coming in June, definitely new things will be announced. Which means Marmalade SDK is going to be obsolete again right after it's released...
 
Regarding current Marmalade SDK with Bridging License, it is perpetual as we promised, you can still use it, forever.
The document site will still be there for 6 months. We can provide you an offline package of the documentation if that makes you feel safe.
The license server will be turned off. We will drop out a patch that allows you to activate it without the server. The patch will be available for 6 months, too. Please remember to download it before anything unexpected happened.
 
Thank you for your attention.
 
Farewell.

 

Have more questions? Submit a request

25 Comments

  • 0
    Avatar
    Fernando Castano

    We need to get Marmalade 8.8. Where can we download if we don't have licence now? We have contacted with you because we need it. Are you going to publish the SDK as free download?

    Thanks in advance.

  • 5
    Avatar
    yuriy

    Any chance you will publish Marmalade SDK source code under some licence and give people who still have live projects written on Marmalade SDK a chance to keep their projects live as long as possible?

  • 1
    Avatar
    MathiasL

    We just bought for $1200 of "perpetual" licences knowing that iOS11 support (iPhone X resolution, mandatory to be featured by Apple) was going to be available in "early summer".

    Please at least open the code to the community if you are not going to use it anymore, so we can update our apps.

  • 0
    Avatar
    De Feyter Michael

    Obviously I am very disappointed to hear this, but not surprised, I guess the writing was on the wall. If you don't continue to keep investing in your product, you'll fall behind and eventually disappear.

    As others have suggested, if you're not intending to sell the Marmalade SDK to a different party to keep supporting it, it would be great if you would release the source code so we can form a community to keep it alive. I for one would certainly be interested in participating.

    Remember that the Marmalade SDK originally started that way, open source supported by a small community of keen developers, back then it was known as the Airplay SDK.
    Perhaps we should rename it back to that then?

  • 1
    Avatar
    Statksn

    I would also request for a source release. Originally when Marmalade SDK was discontinued, Marmalade (UK) promised to provide the source license and an ability to use native Xcode toolchain (which currently is possible with --iosnative option, but locked to debug builds and has a screen watermark).

  • 0
    Avatar
    AG
  • 0
    Avatar
    Bouchard Eric

    I would also be interested in an open source version. I already added a few extensions on my own to support new stuff. I could also help maintaining it alive.

  • 0
    Avatar
    Tim Skillman

    Yes, we would love to keep Marmalade alive under open source too!  So many developers have invested in Marmalade it would probably take off like never before!!  Please don't let Marmalade SDK die :-( 

  • 0
    Avatar
    Krebs Mathias

    Same thing for me, an open source marmalade would be really good news after all.

     

    Edited by Krebs Mathias
  • 0
    Avatar
    Marmalade Team Japan

    Hello everyone, 

    We understand your disappointment, and apologize for any inconvenience that this may have caused you.

    Regarding your questions:

     - Open Source : for several reasons, we don't have any plan to make it open source. Sorry.

     -  Regarding the updates planned in the roadmap (iOS 11, Oreo…).

    Like explained in our Roadmap update in April here : https://support.madewithmarmalade.jp/hc/en-us/articles/115015296867-Product-roadmap-update

    « Please notice that these updates are not part of the Bridging License »

    This was never planned as an update included in the Bridging License.

     

    We are doing our best to provide you the tools, and documentation to let you continue to use Marmalade forever.

     

    Best regards,

     

    Marmalade Team

     

  • 2
    Avatar
    Statksn

    If the source code can't be opened, then please at the least unlock --iosnative option for a release build and remove screen watermarking. This functionality allows native Xcode build and was originally proposed by Marmalade UK but currently locked for debug builds.

  • 0
    Avatar
    De Feyter Michael

    I agree,

    If you can't release the source code, at least give us the ability to continue to use what we have now with an iosnative release option.

  • 0
    Avatar
    Marmalade Team Japan

    Sorry, but we cannot unlock iOS native option or change anything to Marmalade content.

    The development has already ended.

     

    Best regards,

     

    Marmalade Team

  • 1
    Avatar
    De Feyter Michael

    @ Marmalade Team:

    That's not good, this means that the SDK is useless if we want to continue deploying our apps to iOS. $600 well spent on that "perpetual" license!

     

  • 1
    Avatar
    Bouchard Eric

    I agree, I bought the perpetual licence knowing that, yes it had its limit, but that there was a future linked to it. So "perpetual" until "next release is out". Now you just change the terms and say there will be no next release. In reality, this mean our "perpetual licence" will be unusable within the next year or so. In terms of law, this is not considered "perpetual" if you cannot even use it the next year. 

    You are basically saying, thanks for all your 600$, now forget about it. All we ask is take your hard drive, drop it on a dropbox somewhere and we will take care of it. 

    You won't lose any money out of it, it won't cost you any money either. You already decided that you will never improve this codebase. It is not that in 2 years from now it will now worth a fortune ready to be sold to the next company...

    Can you please reconsider your choice again? after all, we did pay you for this, it would be morally questionable that you just drop us saying "not my problem"...

    Thanks for listening.

  • 0
    Avatar
    De Feyter Michael

    Guys, looking at the Marmalade files, it might be possible to modify the xcode.py makefile builder to generate a native release makefile. I'm looking into it since Marmalade Japan has decided on a "take our money and run" option. (I'm very much wondering if this wasn't the idea all along BTW)

  • 0
    Avatar
    Krebs Mathias

    Just wanted to ask if anyone has found a way to modify xcode.py to allow the build ?

    However, I am trying to port my app to openframeworks (see openframeworks.cc).

    It has a similar level of abstraction as Marmalade c++, provides a decent set of tools, and its open source, so no danger of vendor lock in as with marmalade...

  • 0
    Avatar
    De Feyter Michael

    @Kerbs,

    I'm pretty close but I've had to do a lot more than just modify xcode.py.
    I have decompiled and modified almost every pyc file in the makefilebuilder folder.

    Whether I'll be successful depends on whether the s3e libs have to be compiled differently in order to link with the native xcode libraries, I know the native debug s3e library is different but that might purely be to invoke the watermark.

  • 0
    Avatar
    MathiasL

    Can we help somehow ? Help us Michael De Feyter, you're our only hope...

  • 0
    Avatar
    De Feyter Michael

    Hi Mathias,

    Contact me through the feedback form on my website here:
    http://www.ifms-fs.com/contact.html

    I'll share with you what I've got already.

    The more I look into this, the more it seems it should be possible.

     

  • 0
    Avatar
    Andrew Hersee

    I've created a Google Group (Marmalade Afterlife) to help everyone keep in touch and hopefully figure out a way to release updates to iOS apps after the end of this month.

    https://groups.google.com/forum/#!forum/marmalade-afterlife

  • 0
    Avatar
    Andrew Hersee

    To Marmalade.

    Are you able to share with us wether you hit an unsurmountable brick wall in trying to add support for building against iOS 11 (with no new features). I'm hoping you didn't and that this just never saw the light of day due to the larger next release took longer than anticipated and had to be canceled.

    Perhaps you can share some light as to the best way forward for us to release updates to iOS apps in July 2018 when apple require iOS 11?

     

  • 0
    Avatar
    De Feyter Michael

    Hi Andrew.

    I've uploaded my changes so far to the group.

    Cheers,
    Michael

  • 0
    Avatar
    Fernando Castano

    Hi, De Feyter Michael, where have you uploaded your changes? I can't find them.

    Thanks in advance.

  • 0
    Avatar
    De Feyter Michael

    Hi Fernando,

    I'm not sure where they went, I had uploaded them to the Marmalade afterlife google group.

    The post with attachment seems to have disapeared.

     

Please sign in to leave a comment.