We have been “quiet” for a few months, piecing together the new NEO universal app, core UNA CMS update and a handful of new modules. All these updates are a bit different from the regular new modules and bug fixes. So different, in fact that we had to re-think how to package, ship, and support UNA.
I’ll share the observations first, then takeaways, then the news...
Observations
- Native Apps give a huge advantage. While UNA is responsive and can be shipped as a PWA, native apps from App Stores with interactive, platform-specific UI consistently attract more engagement. For social platforms, 8 out of 10 returning users typically prefer native apps.
- React Web App has greater potential. While the UNA classic UI holds its ground, the Next.js web app exported from the NEO universal app repo represents a significant upgrade. Features like data-prefetching, WebSocket updates, aggressive caching, and virtualized lists enable high-performance modern web apps. UNA CMS is a fantastic API server and admin interface, but for user-facing applications, server-rendered SPAs are the superior choice.
- AI is powerful, promising, yet temperamental. The AI Agents module is theoretically capable of creating automations and tools to compensate for missing modules or integrated services. Its potential is immense, but it requires further research and tooling to unlock fully. However, AI often behaves unpredictably, being overly confident when it shouldn’t be, and needs careful supervision.
- Docs are hard, for two reasons. First, while writing docs isn’t such a big deal, keeping them up to date is hard. We make hundreds of commits for each update and many affect logic to the point that docs require updates. the second reason is justtaposed to the first one - people just don’t read docs. The amount of times we have to explain the same things that are already covered in docs over and over and staggering.
- 99% of the issues are “Day 1 stumbles”. Nearly every problem UNA operators report stems from initial setup, hosting environment, or basic configuration challenges.
Takeaways
We need to make it easier to deploy react apps.
At the moment we only build apps under custom professional support agreements. It’s a very nuanced and tailored approach, taking us a number of weeks to prepare backend and the apps for production deployment. We need to make it more accessible for UNA CMS users to launch the apps.
Pre-configured opinionated kits work best.
The way to make deployment easier is to provide an initial configuration that serves an actual use-case. UNA CMS is powerful, but the “anything is possible” can also mean that its not suitable for anyuthing in particular out of the box. So, we need to focus more on the starter kits, tied with matching pre-preconfigured API and React apps.
AI should interpret docs and knowledge.
If we maintain and update knowdlege base continuously, we can train AI to interpret it and help UNA users understand the system.
Steps
UNA 14 Release
The upcoming release of UNA 14 is heavily focused on API, compatibility with NEO apps and the Agents module for AI-automations. We’re likely to have one more RC shortly followed by final release.
Spacenook + NEO Bundle Starter Kit
Spacenook starter kit is getting an update to UNA 14, some configuration changes and most importantly settings pre-set to work with NEO. It will also include a pre-configured NEO apps package.
AI assistant in UNA Studio and UNA CMS
Still quite experimental at this stage, but we should soon be able to provide a built-in AI-powered assistant chat within Studio helping with configuration, as well as a documentation assistant here at UNA CMS.
Share more about ongoing dev
We’ve been to quiet recently, even though in recent months we made more really exciting changes than ever. We should tell more now and show what’s happening. I’ll keep you posted!
It's ever exciting around here Andrey, great to be back in the fray... 2025 is gonna be 🔥
Very exciting news and updates! Anticipating the Phoenix's rebirth 🤩 🐦🔥
The horizon keeps its distance!
chatgtp knows quite a lot about UNA :)
That's true, however not so much about v14 and NEO app - there're many new concepts.
Yes sure this is a brand new development.
But as a fellow user of UNA I felt proud and happy for "it's" interest and good comments about UNA 😊
Exciting developments. Keep up the good work gentlemen.
Looking at facebook, mooSocial, phpFox and all the other competitive platforms (Never mind open-source), one would think you can't get better. I have to be honest, and at times I wish could just buy one of them to ease my life. Well, UNACMS is a different ball game and changed my view and perspective..
When the team goes quiet, knowing the level of intelligence and skills they poses.. it is as if they constantly study market trends and what the latest technology offers.
One can only imagine... and this makes you think twice if ever you wish or consider other platforms for your solution. These guys revolutionize the industry with endless possibilities looking at their UNACMS in the metaverse industry.
Well done and yes, I think it excites all of us...
So these new NEO apps will be available when UNA 14 releases and I can put them in the google play and apple stores?
That's the plan.
Sounds good!
Does this mean that the Una 14 front-end as well as spacenook and other starter kits will utilize these features?
I personally like the starter kid idea with SpaceNook, but how do I migrate my current system into, going back a step just to adapt the starter kid benefits as it stands.
NEO works with UNA API, but UI for modules needs to be adapted so initially not all modules will be compatible. The Starter Kits will come preconfigured for combined deployment UNA and NEO web app, with endpoints enabled for native apps as well.
Starter kit is just a set of settings. You can do the same config with your current installation.
Hey @Andrey Yasko , Am I happy to hear from you..., I hear you, well not quite. I could explore Messenger and boy, it got me exited, because my understanding was if I build my current platform from it, it would mean I have that module legally, and why not, just saying... anyway, it's good to hear from you.
Now I get it. I've upgrade SpaceNook to 14.0.0-RC3, but Messenger was the only module that didn't update even though the latest version for it is available.
Andrey, I guess what I'm wondering is if we start off with the current UNA core/Artificer template and configure our own "starter kit" instead of using a pre-configured one, will we have to do any extra work to get NEO compatibility if we continually update to current versions of the core/modules?
Does this mean there will be a standard, UNA-branded app that users can download to use with our communities (eg like phpFox) or does it just make it easier for those with the technical skills to make their own app?
D
I am currently using Spacenook 13.01. Based on the information, it seems the NEO Starter Pack will be coming soon. I am in a dilemma: should I update now to Una 14 and then do another update for the Starter Kit, or should I wait and do the update all at once? Any recommendations? My also waiting eagerly for NEO app so that I can give user a new experience on mobile device.
Starter Kit is just for starting out. Once the site is running you just update UNA. Spacenook packages are not any different from UNA other than configuration settings that you get from the get go, and probably would change since initial installation. So, just update UNA.
D
Hi Andrey,
Thank you so much for your reply — much appreciated. It will take a few more months for me to fully understand the upgrade process. This is my first upgrade since I started using UNA. Based on your comment, it looks like I should go ahead and upgrade, as I am already in the launch phase of my website and not starting fresh.
Question: Once the NEO app is released, I can still use NEO Package for my website, correct? I assume the NEO app will be for the entire UNA platform and not just for Spacenook?
I refrain from praise and try to provide only constructive criticism.
“People just don’t read docs.”
I do think so as well, but I do. However, there has been so much written that one easily gets confused and many times is often fed with misinformation. The official guide should be updated as questions have been answered, because those questions are going to be asked again.
99% of the issues are “Day 1 stumbles”.
Absolutely. I acknowledge that I have contributed to your frustrations. I want to commend @LeonidS for being so patient and helpful. However, I believe that once the questions and problems he addresses are resolved, they should be immediately included in the user manual. Doing so will make his job much easier and will significantly reduce users' frustration levels.
We need to make it easier to deploy react apps. Yes, please.
Pre-configured opinionated kits work best.
Restrict the areas where users can access settings that might disrupt their sites. My primary concern is how my site displays, along with managing user features and commission percentages. Make the user configuration interface easier to understand and set up.
I completely agree that while "UNA CMS is powerful," the concept of "anything is possible" can create problems if we want to provide and maintain everything. My creative mind envisions many possibilities, and I will test your system to its limits.
I recommend starting with the core functionality of a basic blog app that allows users to insert and attach photos and videos, along with other possible attachments. In addition, you could offer additional applications developed by UNA and other developers at an affordable price. It would be wise to manage these developers and their products effectively, taking a percentage commission from their sales and subscriptions while ensuring compliance. Furthermore, overseeing communication between third-party developers and their clients could also be beneficial.
@Romulus made some excellent suggestions. This way, the time spent on explaining how things work would fall mostly on them, allowing them to provide support and faster turnaround time.
I have worked with several frameworks, and I can say that PrestaShop is a standout example of a well-focused, well-managed framework. It looks great, and when they list a third-party app for sale on their site, it functions seamlessly. They maintain their focus, and I've rarely needed assistance from them—perhaps only three times. Their installation process is smooth, and the configuration is clear and easy to set up.
Most users are not programmers, and they are your target market. By simplifying the process for them, you will see your business grow. I believe that experts who wish to contribute to the core should work on a separate system in GitHub.
Another option that you should consider is to create a closed system where the core is purchased and maintained through a subscription model. I'm currently using Website X5, which is very user-experience-focused, multi-browser compatible, and mobile-friendly. I can roll out basic websites overnight and impressive sites within three days. Add-ons are available for an additional fee, but updates for all are included in the subscription.
I've asked you multiple times to examine their user interface, particularly how they manage the user interface for the mobile layout.
UNA is a powerful and impressive system, but it takes a long time before one can launch their community page, which may cause you to lose prospective users and revenue. I’m 6 months down the line, and still, I cannot launch the site due to all the loose ends and broken features.
I've been with you since 2017 (when I used Boonex Dolphin) and will continue to support you, as I believe something great will ultimately come to fruition.
I switched to UNA due to the mobile limitations in Dolphin. Financially, this has been quite an expensive setback for me, as very few of the 120-plus apps I purchased (some of which are quite useless) are available on UNA, and those that are must be purchased at full price without an upgrade option from a Dolphin app at a reduced cost.
What is sad for me, and I do not know the internal differences you had with @Jerome Mingo, but it was such a pleasure to work with him in Dolphin days. It would be so great if you can sort out your differences with him or even offer him a good deal to become part of the UNA core development team. He, in my eyes, is very talented, well qualified, and experienced to roll out awesome apps. Even his apps that I have purchased for UNA, have great configuration panels are wonderfully integrated into the front-end. I’m sure many will agree with me.
Mmmm, and don’t forget about @Romulus. He is single, has no girlfriend, and is fully focused on the work at hand. 😜
@Andrey Yasko Congratulations and best wishes for your future endeavours! Thank you to you and your team for your dedication and effort in developing the best social media framework available.
Ps.
Please implement a floating text editor menu bar above the highlighted text, along with a comprehensive list of properly sized emojis. These small enhancements can significantly improve our users' experiences.
Additionally, evaluate how many operators find success with a "basically free" system and are willing to offer UNA shares in their businesses. While I am not successful yet—my site is still in pre-launch—I recognize the importance of UNA and your support in helping me realize my dream.