This isn't a particularly astonishing scenario. However, I chose it for a reason: it requires two cases of what is typically non-core functionality to intersect (mobile CMS, and gallery support), and our competitors utterly fail when this needs to happen.
ocPortal is built on the basis that all the features need to work together, whilst other free CMSs are built by a core team and the useful extra features (like galleries) are done by third-parties. The chance of any two third-parties actually working together to create sufficient consistently is very low, as I will demonstrate.
I will be doing a very quick analysis for the “top 3” CMSs: Drupal, Joomla, and Wordpress. I am not expert, and I don't think people would appreciate me wasting my time spending too much time researching this. Therefore I am going to get my answers using Google and rely on people commenting below to correct me if I am mistaken anywhere.
Using Google, I went for a search term pattern: “<product> gallery mobile”.
The top appropriate results were:
- Wordpress: http://wordpress.org/support/topic/nextgen-gallery-mobile-version
- Joomla: http://forum.joomla.org/viewtopic.php?p=2479620
- Drupa: http://groups.drupal.org/node/109894
You can repeat this experiment yourselves. Of course, Google's results might change, but I think for at least the next few years at least my analysis is going to stay correct.
To be clear, in case my implication wasn't obvious, ocPortal has mobile CMS support and gallery support out of the box. It's not a feature we advertise, it's just one of many scenarios that “just works” in ocPortal. That's my point: ocPortal does what you would expect for any particular reasonable situation, other CMSs typically do not. And, ocPortal is fully Open Source, so you don't need to pay a penny for it.
This was article 8 of 8 in my "Web industry Exposé" series of blog posts.
If you think it's good advice, please share this link with others. If you think I'm wrong or have something to say, please discuss below.