The future of Cwicly

[Louis]

Thanks to everyone for their positive responses, much appreciated. I’ll be going into more detail in the coming weeks on what this new chapter for Cwicly will bring.

@kgeee

Cwicly support stopped responding, they closed Discourse, disabled Facebook comments, and removed any chance of getting in touch with them.

This is not true. The discourse was closed for a week or so, and our support team was available all throughout this period, keeping communication open at any moment for our users.

Please feel free to open a new thread if you want to continue this conversation, as I believe the focus has shifted from the original subject at hand.

@marc

It would be super helpful to get your perspective here. I’m about to start a couple Wordpress projects and I’d LOVE to build them using cwicly, but I’m worried that in a couple years you simply won’t have the financial resources to keep providing compatibility updates and security patches. I know you promised these updates and patches for 2025 and onwards, but if at some point you there’s no money left, then you won’t be able to do that.

I’m not asking you to lay out your entire finance plan, of course, I’m just trying to manage my own expectations towards cwicly. To what degree can I truly, realistically rely on cwicly for building websites that I’ll be maintaining for at least 3-5 years? How will the cwicly team manage to stick around for that long without any new revenue?

Again, I love building sites with cwicly and I want to keep doing it. I’m not asking these questions to criticise cwicly or the team in any way. I’m simply faced with an important business decision here and I’m missing a crucial piece of the puzzle to be able to make that decision.

So if there’s any more details you can share with us, Louis, I would appreciate it very much

Thanks for your post, @marc.

I understand there are uncertainties that need to be resolved for our users to make informed decisions.

We will no longer generate revenue from selling Cwicly licenses. Instead, transitioning to a free or open-source model will enable us to adopt a new revenue strategy.

Maintenance, patches and support are already funded for the next few years.

As for new features and improvements, the success of this transition will determine our ability to develop them. It would be misleading to claim a 100% guarantee, as multiple factors are involved. This uncertainty may influence your decision to build with Cwicly in the future, but I prefer being transparent here.

The next few months should provide a clear indication of this transformation.

@antonijo01

Can we maybe expect a roadmap with possible new features in the future?

Hello @antonijo01,

The focus for the next few months will be addressing the main bugs that are still apparent in Cwicly. We’ll also be reviewing the onboarding process as well as reviewing the design library content. Tailwind and components will also be the main focus during this time.