Moovweb XDN vs. Webix UI

It depends on who you are. If you are very small it won't be worth the money. If you have a very cranky site with nested tables coming out of every orifice, maybe you should look at a replatform or desktop rewrite first. If you have a site with vast numbers of custom content pages, it will work but may not be cost effective. Moovweb is well suited to you if you need the ability to control mobile experiences and respond to changes in mobile and the demands of mobile aware executives who want to move more quickly than your current IT processes allow. It is well suited if you need something quickly but also want the option to bring mobile development and support in-house some time in the next year or two (which you should). It is well suited if your desire to improve a responsive experience has been thwarted by internal fears over the impact that it might have on desktop. It is well suited if you want to experiment on mobile but do more than just change the color of a button or make a font larger. It's very good at letting a UX team try things out and see what real customers do.

If you need to create an interactive data report, optimize a workflow, handle hierarchical data or make calculations in a powerful spreadsheet, you will find a proper widget for your needs in the Webix UI library. If we want to display data in various forms Webix UI layouts and widget help to organize a web page and define its overall look-and-feel.

Incentivized

• Moovweb takes the time to really understand your needs and challenges and is willing to work with and address them. They are partners during and AFTER implementation.
• Moovweb and their implementation partner 64Labs has a fantastic response time and work ethic. They really will do what it takes.
• Moovweb takes the time to share their product road map with customers.

Incentivized

• The Kanban Control allowed to implement a compelling task management system with little effort.
• The Chart Control made it easy to create our dashboard and it was a lot easier than using D3js as we did before. D3 allows a lot more flexibility but it takes often 10 times longer to get a chart done than using Webix.
• Support at Webix is very helpful and responsive.

• Depending on how your site is built and maintained, there may be a different solution that will be a better option for your business and customer needs.
• At the end of the day, this is another layer that is added to your development plan and time to ensure updates work across multiple devices. Moovweb is really good about the turn-time for these updates, but there still needs to be the added QA step for M&T optimization per release.

• None at the moment

Personally as a Mobile Architect I am a huge proponent of building mobile-first responsive websites. I will always fight for a lobby for businesses to build sites with all devices in mind and not focus their attention on desktop driven sites which are then adaptively scaled to meet the demands of the business, in my opinion leading to a never ending cycle of building separate media queries to compensate for every device the business chooses to market to

Incentivized

Good set of customer success people combined with the flexibility to use high-quality onshore partners if workload increases at busy times. I think Moovweb's support efforts are pretty solid.

Webix UI is a cross-browser, cross-device JavaScript framework which makes it easy to build a complex Web UI. Most features work as expected. While working with large datasets, you can load data dynamically to reduce complexity and improve performance. It provides a set of integration extensions that allow you to add third-party tools into an application.

Incentivized

1. Don't spend weeks in design. Because of the way the technology works nuances of design can change very quickly further down the line. We have changed the look of the product list for a client a week before launch.
2. Push for getting the project into UAT within four weeks of the kickoff of the project. There are few retailer projects that need to take more than that. In my experience the more concentrated the timeline the more effective the implementation.
3. Check that there are no major changes planned on desktop during the time of your implementation (another reason to keep the development to four weeks).
4. If you have custom mobile content requirements, get them to your implementer at the start. Moovweb is great at heavy-lifting existing content, but your implementer will need to recommend solutions for custom content that will need to be tested. Get these requirements out at the start.
5. Make a list of your desktop plugins. Moovweb can handle them all, but they can be handled in different ways
6. If you have Paypal/Google Wallet and want it on mobile as part of your project, talk about that early on.

This is the only mobile technology we have used. We went through an extensive research and vetting process. In the end Moovweb was the best choice for technology and business needs. We considered the following companies: Moovweb,Mobify, Usablenet, Mad Mobile, SKAVA, Wompmobile. Forrester has a mobile infrastrucutre services report that could be very helpful.

Incentivized

React was too time consuming. Kendo was another good one, but more expensive and seemed less responsive. [Sencha's] demo didn't seem to justify the price.

• The implementation was 4 months from start to finish. Mobile is about 10% of our visits today and our mobile revenue for the first half is about $200K so we will have a payback in 1 -2 years.
• Moovweb is not the most economical solution out there. It is one of the most comprehensive for sites needing all their content available for mobile.

• It saved us 1000s of USD for just using the Kanban Board instead of developing it from scratch.