Hi, I'm discovering UNA and trying to figure out if it fits my needs, comparing it to humhub.
I'm interested in views concerning these two platforms, when compared to each other.
I'm curious about the una interface : I've noticed that when I click on almost any link, the whole page reloads, instead of modern webapp interface like humhub where there is only partial page load : is it a limitation of the platform or is there any plan to "ajaxify" the platform ?
Comments
There are many similarities and some key differences. I’ll point out the ones that I can observe, though generally we are not in the habit of researching competing products, so I may be wrong in some instances.
1. HumHub is using a copyleft license for basic edition and commercial license for enterprise edition. UNA is using MIT license for everything. It’s more permissive.
2. HumHub seems to be designed more like a traditional CMS with customisation done via configuration files and admin panel Settings. UNA has a powerful configuration inferface - Studio, where you can chnage site pages, permissions, navigation, languages, etc without editing files or code. Content Administration is separated into user-interface, so it is possible to create teams of admins/moderators with different dashboards.
3. UNA supports multiple profiles per account, multi-account Org profiles, as well as typical Permission levels.
4. “Contexts“ in UNA can be of different types - Spaces, Groups, Events, Channels, Profiles - was hey can have different logic and can be used simultaneously.
5. As for the “Ajaxy” interface - this is done gradually for different pages and components. HumHub is primarily designed for group/company collaboration, where content is is exposed publicly and participants are trusted. They can thus turn more of their UI into an SPA. UNA is designed for large-scale communities with mixed privacy - there can be public content as well as private - so extra care is needed for handling links, link sharing, routing. We are working on gradually implementing more and more interactions with inline loading. Also working on JOT - fully ReactJS-based frontend, which will handle all modules within the single page. UNA can basically be treated as a headless CMS providing database structure and permissions, while UI can be built any way you want - PHP, React, Swift, etc.
6. From what I can gather HumHub doesnt have iOS/Android apps in any edition. This is common for systems designed for teamwork as opposed to general community.
In short, HumHub is for team collaboration. UNA is for full-featured social media communities.
Also, I should note that it’s not a direct 🍎 to 🍏 comparison. HumHub is more specialised and compares to Slack, RocketChat, Basecamp. UNA handles wider scope of usecases and can include something like HumHub as an integral part. UNA is best compared to Drupal, with extra focus on community as opposed to content.
I have humhub installed on a site and for the purpose it is great. It is different in architecture from UNA as it is based on Spaces. I like that you have some useful plugins that installs easily and it has some cool chat systems that you can use with one click install.
mine is at http://musthavepets.com where I am testing it and working on a few things.
Andrew Boon gave a good summary above.
Best thing to do is install them and try them out.
Try to find Oxwall or its branch Oxwall Engine. It was my favorite Social Network CMS until they stopped development and went commercial with skadate.
There is also Jamroom, Drupal, Joomla or WP with their community builders and numerous plugins.
Hello @Andrey Yasko
I am always grateful for your help
I think the only point where una is inferior to humhub is the notification function.
una's notification function is useless because it can't be categorized and gets buried.
On that point, humhub allows you to classify things so you won't miss anything.
I wish the notification function was a little easier to use.