My developer team and I have decided that we would like to develop a MUSE compatible software, that would replace MUSE, if there is enough interest. I’m creating a petition to see if there is any.
As a lot of you, we have built our company around MUSE partly. About two years ago we have invested time and money to develop this branch. We were stunned when we saw the news that ADOBE has announced the discontinuation of the software, that I regard as a unique solution, even if it has its own faults.
When we decided to develop this branch of the company, we have investigated different software products. Some of those has never worked quite as well as MUSE, others had restrictions about where one could keep his or her site, or they were more expensive than MUSE, or there were not enough components to choose from etc. Personally I liked the widget system very much, as a user, I liked the simplicity and freedom it offered, which were supported by MUSE as a framework.
According to what ADOBE disclosed, they are going to support MUSE for another year.
But how am I supposed to build a site with it now, if I know full well that it is going to close down. How much work will it be to move the site? How much wasted money, how many widgets will I lose?
Someone asked why don’t we build the software again? A MUSE compatible software. We have spent the following days investigating the question, if it is possible and if yes, how exactly.
Long term goals
Who should sign the petition
I hope we will have a successful campaign, and we can create a software that will replace MUSE. You can go to this address to sign the petition:
Thank you for reading this petition. – Wesselenyi Rendszerhaz Ltd. team -
Who should sign the petition
- According to our calculations, we can reliably develop the software. It would take about 12 months to reach beta. (By the time ADOBE pulls support)
- After the beta, It would take another year to finish the product.
- It would take about 2000 supporters to be able to get started on the development of the project.
- We intend the start a crowd-funding campaign to cover some of the costs of development. It costs 280 dollars to pay for a year of ADOBE MUSE. For the program we intend to develop, you can subscribe for 100 dollars a year, in our Indiegogo campaign.
- The more people supports our campaign, the more resources would we have available to us, lowering the risks.
- With this petition, we intend to see how many serious supporters we have. If we attain 2000 supporters, we will start the Indiegogo campaign.
- Please only sign the petition if you seriously consider paying 100 dollars a year for the yearly subscription.
I applaud your initiative, but what about the risks to those people whom support / fund it ?
Macaw was a great example of this danger.
2,752 backers pledged $275,929
Those 2,752 spent money and received a unfinished buggy product, the company sold out and ceased to exist, the supporters were left with empty promises. Not a good return on investment at all.
Wappler is another crowd funded project with unknowns, but it is backed by DMXzone so maybe better odds than Macaw.
With Muse users already not feeling good regarding the investing of their time, money and effort into and with Adobe Muse, I ask what is the assurance to them, if any from you?
Again I applaud your initiative but that aspect should be seriously considered by Muse users.
In addition to my above already stated sentiments.
It sounds like it will be a desktop app and not web based, thats good. But will it work from raw source project files (HTML/CSS/JS) or have a closed proprietary file format? Thats important in case it does not succeed to fruition. Will Muse users that adopt it in their workflow and decide to depend on it be able to easily take their files and projects and work with them elsewhere in other software?
Again for Muse users, that will be important to not be locked into something, given what they are now experiencing.
Looking forward to hear your answers on these things.
I know of 3 3rd party softwares that already meet most those points like open a .Muse file and interface... the 3rd party widget idea is not realistic and I can only assume you didn't get advice from a code expert before making up that list
best of luck with it