Adobe Experience Manager is a combined web content management system and digital asset management system. The combined applications of Adobe Experience Manager Sites and Adobe Experience Manager Assets is offered by the vendor as an end-to-end solution for managing and delivering marketing content.
N/A
SharePoint Designer (discontinued)
Score 6.0 out of 10
N/A
Microsoft's SharePoint Designer was a tool for developing SharePoint applications that has been discontinued.
N/A
Pricing
Adobe Experience Manager
SharePoint Designer (discontinued)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Adobe Experience Manager
SharePoint Designer (discontinued)
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Adobe Experience Manager
SharePoint Designer (discontinued)
Considered Both Products
Adobe Experience Manager
Verified User
Anonymous
Chose Adobe Experience Manager
End to end capabilities as well as integrations with upstream and downstream systems to make work flows, easier and faster time to market
SSO is one fits all, so we don't have to have a separate SSO for each application of Adobe The integration with Analytics works perfectly and bring directly value really quickly Target remains more complicated to set up, but can also bring a lot of value once integrated with …
Adobe Experience Manager is what I use most frequently. While the other tools I listed above are important, they are ultimately a secondary tool utilized on a need by need basis where as AEM is what we use daily for content creation, content updates, content optimization, etc.
AEM is comparable to Sitecore and less agile than Bynder, but Adobe products were already being used across the org and adding AEM allowed us to link it all together.
I haven't used anything else like this. I use different products for workflows and forms, but they aren't listed in the listings for this page. Instead of using it for workflows or forms (deprecated 2 years ago), I use Nintex. For everything else, I have what I need in the …
These products are very good alternatives to SharePoint Designer but SharePoint Designer stacks up when you are using it for on-premise SharePoint environment.
I prefer InfoPath for designing forms for use in SharePoint over SharePoint Designer. I have not used SharePoint Designer for designing pages in SharePoint. I have found it easier to work directly in SharePoint. Granted I have only had the product for a little over a year.
I'd say that Nintex is a lot easier to configure and identifying errors is less complex than SharePoint Designer. In addition, an alternative that developers may prefer using is Adobe Dreamweaver which is also a web development tool. A third option is Coda, a text editor that …
SharePoint Designer is somewhat inferior when compared to a purpose-built third-party tool like Nintex. Even though Nintex leverages built-in workflow engines (SP2010 and SP2013 depending on platform), it builds on top of that and adds many useful features.
Nintex Forms and Workflow are both very robust tools, but cost for some clients can be prohibitive. Nintex does not provide tools to manage SharePoint sites, lists and libraries.
Both K2 and Nintex provide a powerful platform to build and run business applications that integrate seamlessly with SharePoint; business apps typically consist of workflow, forms, data and reports. The type of business apps range from simple document approval workflows to …
Both Nintex and K2 Blackpearl are great products in their own way, but they are expensive. The pricing models for the SharePoint Online environment is very expensive for how Holiday uses workflows. Nintex's pricing model is by the number of workflows in your tenant, and I …
There really isn't a holistic, complete SharePoint Designer replacement currently. You can utilize several different tools and piece together the functionality of Designer. No one really "selects" SharePoint Designer, it is just a necessary evil. For O365 subscribers, Flow …
SharePoint Designer is the only tool of its kind that I feel 100% comfortable using. Compared to the Nintex workflows/forms, SharePoint Designer has much more increased functionality and ease for an IT-type user like myself. I think it has a much better and easier to navigate …
As I said before, I didn't select SharePoint Designer per se, but I did (and will continue to) elect to sometimes use Designer rather than create deployable solutions in Visual Studio.
Designer could be called the lazy person's tool for modifying SharePoint. Solutions created in …
I'll answer the second one because I mean, the first one I don't have an issue with. The second scenario is we oftentimes have the need to spin off very small campaign style sites or sites that generate leads but are unbranded and that sort of thing. So that's hard to do in AEM because you have to then create another organization within AEM to do that. And we're talking about sites that are maybe five to 10 pages in size. So we've been investigating Edge, but then that's a different workflow, so we'd have to train people on that. So it would be nice if there was something within the AEM structure that could allow you to do something very similar to Edge, where you make some small micro sites that are not necessarily branded, that you could still host within the platform and not have to retrain everybody on a completely different platform.
Well Suited - WORKFLOWS! To a SharePoint Developer, workflows are like a hammer to a carpenter. If there is a business process that needs automation, the first thing I look to is what are we automating? What/where is the data? How can we minimize the number of keystrokes by end-users to get from the start to finish? The answer to all of these is "build a workflow". With the introduction of "Call HTTP Web Service" action, you can now access data anywhere in a site collection and consume it in any site, on any list, for any form. SharePoint Designer Workflows makes the SharePoint world go round. Less Appropriate - Building SharePoint Pages I have attempted to use SharePoint Designer to build custom pages, but it just is the worst tool to use. There are many other tools to use to develop customized pages. The techniques of designing custom page layouts, CSS files to populate in pages, JavaScript Snippets for pages have changed so much over the years, and SharePoint Designer did not change with them. In fact, it is my opinion the 2013 version made it 100 times more difficult than the 2010 Version.
It allows us to scale so that we can make a change on a global footer. And it applies to all of the different property websites. It allows us to set up components and compartmentalize things in a way. The big thing is that it's scalable. And then it also ties into Adobe Analytics and other Adobe products. So we are a complete Adobe shop. Every Adobe product that we can use, we use. I don't think we do it for marketing so much, but for doing target testing and analytics, data scientists are using the same product and so it all speaks.
SharePoint Designer offers more granularity of customizing a workflow that is more sophisticated solution that can effectively delegate tasks to responsible parties and reflects status updates of task status.
SharePoint Designer allows SharePoint professionals the ability to customize a SharePoint site with HTML5, CSS3, and JavaScript that can be integrated in .ASPX pages.
SharePoint Designer offers form customization where Office products such as Word, Excel or PowerPoint cannot meet specific government requirements and or expectations.
easier way to make universal changes for multiple websites at a time (ie pushing out a new experience fragment to all as opposed to having to individually add to each site)
easier way to get site images to look and be sized exactly as I want directly from the site page editor
Navigation between sub-sites and beyond the entry point is not seamless. I find it difficult to get to the root of a directory structure if I have not started there.
Would love to be able to do WYSIWYG in some form. I have only used it for a year but I have not found anything fancy to do.
I would like to be able to work in a development site and easily move to the production site.
We had and still have a fantastic experience using Adobe CQ. Lots of flexibility, great integration with other Adobe products we already use and a powerful technology make it a great fit for our corporate environment. Also as the community grows, it makes it easier to network with other developers and users to get new ideas on how to continue to get the best out of the software.
Sure there are a few quirks in the interface, but once you learn them, building and editing pages is fast and efficient. Once you have the content and the planned design decided (how the pages will look and which components you will use), page builds and publishing are quick. I was able to build a 10-page specialized site with cards built using the list component in an afternoon
Being part of Adobe Suite means you are already notified when the tool has any outages. However, I have never faced unplanned outages. Whenever you face any issue with the site, it is clearly stated if there were any planned outages and how quickly you will be back to normal. So, I will say that even the outages are planned and managed in a great way like their other services.
With respect to performance, Adobe experience manager is one of the best in the CMS space. We didn't observe frequent slowness on platform, however the systems which are accessing experience manager should be of good specifications without which slowness would be observed. Adobe experience manager works well in integration with other solutions, unless the destination application is designed to trigger frequent calls to AEM.
Adobe Experience Manager, in all its capacity, is a great alternative to any other CMS you are using. It helps in rapid development and makes life easier for maintaining the website for multi-language sites. Technical know-how is eliminated at content authoring. Better documentation in terms of live examples with videos would be appreciated.
Support is good from Microsoft. They are quite responsive when we raise a ticket but SP Designer support will be ended by Microsoft in the near future as they have got new techs like PowerApps and Flow to achieve the same functionality SP Designer does and even more than that.
Depending on your individual needs, It is really quite simple to create an authoring experience for a website that looks really good. I have been part of many implementations and many teams and have seen many projects that were super successful and others that were not implemented well. AEM has room for a lot of flexibility in the implementation process compared to other CMS like SharePoint
SSO is one fits all, so we don't have to have a separate SSO for each application of Adobe The integration with Analytics works perfectly and bring directly value really quickly Target remains more complicated to set up, but can also bring a lot of value once integrated with the rest of the Adobe platform The fact that the solution is Cloud services is also a big advantage for maintenance
In order to simplify our internal workflows, we have installed additionnal tool for our SharePoint platforms : Nintex Workflow and forms. Compared to Nintex, SharePoint Designer is very far away. I am only talking here for 2 main features of SharePoint Designer : - Workflows - Forms But for these 2 features, Nintex is way above SharePoint Designer
With workflows alone we have had a positive ROI because it gives us increased functionality and value with a smaller amount of development time needed.
The testing of workflows or pages is more structured and we have less base cases than a ground-up customized development solution.
Occasionally, we will have a negative impact on our ROI based on the work-arounds needed to make SharePoint Designer work for a specific project, but overall there has been more positive impacts than negative.