Originally, Adobe AIR was the only game in town, and its blend of flexibility in platforms it could publish to (PC, Mac, iOS, Android), ease of use, and familiarity made it the clear choice. Now Adobe no longer supports it, and we’ve found the transition to Harmon unworkable …
We already use all the other Adobe products so it was an easy choice to use AIR for our programming type of programs. As we used it more, we found that it was very simple to learn/the learning curve was not very steep at all. We honestly didn't look at any other options, …
Adobe AIR does not support Windows phones but works well on both Android and Apple iOS. It enables developers to build and deploy good quality applications to mobile platforms for a majority of mobile users and allows developers to build working prototypes in a relatively …
There are definitely other platforms out there that are awesome but Adobe AIR is just what our other developers were used to using but we do have some success.
Generally stacks up fairly negatively, program definitely has its place, I appreciate what it can allow but now most desktop apps are fine enough as browser based experiences or for personal use mobile is the way to go. Air isn't the best environment for that.
Originally, Adobe Air was a great choice for us to build mobile titles from prior web titles when compared to tools such as native iOS with cocos2d. We were able to get games stood up much faster than our competition and out to market to make money. That said, as Unity improved …
Adobe AIR is more friendly to a serious programmer because it supports core programming methodology in a way that Unity does not. Both AIR and Unity have a hidden underlying layer of event management code that can add performance costs. However, Unity is more friendly to a …
Since Adobe AIR can be used with the Flash IDE, there are not many other solutions with such a robust toolset. The ability to import layered photoshop files directly onto the stage, and then ability to animate and create movieclips within that IDE is an extremely valuable …
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 …
Adobe AIR is well-suited for a developer who is already familiar with Flash and AS3. It is well-suited for 2D app development using Starling or another third-party graphics library. However, to be used appropriately and avoid errors and poor performance, a basic understanding of programming principles is needed, so it's not great for a designer who hasn't studied a lot of coding.
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.
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.
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.
Although Adobe AIR is just an SDK without an actual "UI" it's commonly used within Flash, Flash Builder, or FlashDevelop. Considering the integration with Flash IDE, there are very few tools that can compete with its features.
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.
There are definitely other platforms out there that are awesome but Adobe AIR is just what our other developers were used to using but we do have some success.
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
Using Adobe AIR allows your team to be comprised of Flash/ActionScript 3 developers, which can be easy/cheap to find compared to other disciplines (based on location). This can lower the bottom-line in terms of engineering costs.
As the Adobe AIR SDK is free to use, the cost of entry is basically free. Additionally, the Adobe AIR SDK may be used in conjunction with a free IDE, such as FlashDevelop, making the entire stack completely free to use.
One negative impact is the stigma against Adobe Flash/AIR. Due to Adobe's less than stellar track record (in terms of support and security) with both Flash and Flash Mobile, there are numerous clients that we've dealt with, that refused to approve Adobe AIR as a tool.
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.