Moovweb XDN vs. OutSystems

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.

Well suited for internal exposure of business processes (invoicing, API layer to other systems, customer maintenance etc), whether a UI is required or not. Not so well suited for full fledged web design. An OutSystems application must serve one particular business need, if gets too much functionalities and responsibilities it tends to get chaotic and complex.

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

• Developing end user interfaces with ease and speed with a modern look and feel.
• First class low code development to reduce time to market with visual programming
• Their technical support team is fast and responsive. We've yet to have any issues they could not resolve.

Incentivized

• 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.

• Price – The licensing model of OutSystems is very expensive and not suitable for small scale developments. This is offset by the time to develop and stability for larger scale developments
• Flexibility on PaaS version – The PaaS hosted version of OutSystems limits your flexibility to access the front end and backend database systems which can significantly restrict your options on high data volume developments or where anything requiring slightly out of the ordinary access is required
• Same price for PaaS and self-hosted system. Licensing model dictates that you pay the same price even when you host the system on your own hardware which effectively means you pay more to manage the infrastructure yourself

Incentivized

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

We are very happy with OutSystems and our developers deliver good work. OutSystems lets us build new software on a regulare (2 weekly) basis, which is highly flexible and adjustable. Even without very much experience, our developers manage to build usefull software, which is working a lot better than our previous (legacy) software.

I am really happy using OutSystems in my work. It gives me the opportunity to create good working software without having had very much IT-experience before. It also made me more interested in the background of IT and learning different languages.

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.

The tech support is very reachable. Usually by [email] from but also by phone if needed. We had some difficulties at the start with understanding "what our machine was doing" under high performance load. After some good sessions understanding our needs they delivered good solutions for our problems we had in the beginning.

Excellent material full of hands on that improve the understanding of the platform.

The online training material is well designed and explanations are step by step, helping trainees to understand and follow each exercise and new concept.

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.

In a large company, patiently and consistently work the behind the scenes politics with business and IT partners across the firm.
This is transformational - you will need a solid set of key business partners to lock arms together to move forward.

Incentivized

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

I tried to use WordPress with some success. Also looked at Joomla. But when I saw OutSystems I knew I had been wasting my time there. It takes you longer to get going with OutSystems - but even I as a novice realized immediately that Outsystems is simply in another league. Outsystems is powerful. (Can you compare WordPress and Joomla to Outsystems - I don't think so).

• 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.

• The ease of use of the OutSystems development process has been the biggest ROI for us. We have developed our Framework product and maintained/enhanced it with only 4 workers.
• OutSystems has enhanced their product very significantly over the last 4 years. They have gone from a simple to use tool to a very simple to use sophisticated tool that covers the standard mainframe-based computing apps and the apps used on handheld mobile devices all using the same basic set of development tools.

Incentivized