512
edits
Changes
Technology Trends/Low Code Application Development (view source)
Revision as of 13:23, 18 July 2019
, 13:23, 18 July 2019no edit summary
</th>
</th>
</tr>
</tr>
<tr><td colspan="2" class="logo">[[File:Low_Code_Application_Development_logo.png|200px]]</td></tr>
<tr><td colspan="2" class="logo">[[File:Technology_Trends_-_Low_Code_Application_Development_logo.png|200px]]</td></tr>
<tr>
<tr>
<th>Status</th>
<th>Status</th>
<div class="mw-collapsible-toggle btn" style="float: left; display: block;">
<div class="mw-collapsible-toggle btn" style="float: left; display: block;">
<div class="toggle mw-collapsible-toggle-collapsed" role="button" tabindex="0"><span class="mw-collapsible-text">Cacher la Vue Détaillée</span></div>
<div class="toggle mw-collapsible-toggle-collapsed" role="button" tabindex="0"><span class="mw-collapsible-text">Hide Detailed View</span></div>
</div><br><br>
</div><br><br>
<div class="container">
<div class="container">
<div class="row">
<div class="row">
<div class="col-sm-4">
<div class="col-sm-6">
[[File:Technology_Trends_-_Low_Code_Application_Development_Forrester_Wave.png|center]]
[[File:Technology_Trends_-_Low_Code_Application_Development_Forrester_Wave.png|center]]
<p class="source">Figure 1 The Forrester Wave: Low-Code Development Platforms for AD&D Professionals, Q1 2019. Used without permission.</p>
<p class="source">Figure 1 The Forrester Wave: Low-Code Development Platforms for AD&D Professionals, Q1 2019. Used without permission.</p>
</div>
</div>
<div class="col-sm-8">
<div class="col-sm-6">
<table class="wikitable hypecycleTable">
<table class="wikitable hypecycleTable">
<tr>
<tr>
</ol>
</ol>
<p>Websites of the low-code tool leaders typically provide reference customers, and these include numerous prominent banks, insurance companies, airlines, government departments, and the US Army – though in most cases no details are given about the precise application domain. Most of the analysts’ reports, as well as self-reporting by OutSystems and Mendix, indicate that 88% of companies are adopting low-code, while 74% of those companies are integrating the business side into low-code development, thereby directly involving the clients who dictate the requirements .</p>
<p class="inline">Websites of the low-code tool leaders typically provide reference customers, and these include numerous prominent banks, insurance companies, airlines, government departments, and the US Army – though in most cases no details are given about the precise application domain. Most of the analysts’ reports, as well as self-reporting by OutSystems and Mendix, indicate that 88% of companies are adopting low-code, while 74% of those companies are integrating the business side into low-code development, thereby directly involving the clients who dictate the requirements.</p><p class="highlighted inline mw-collapsible-content"> ([https://www.mendix.com/why-developers-should-embrace-low-code/ Example])</p>
<div class="container">
<div class="container">
<div class="row">
<div class="row">
<div class="col-sm-4">
<div class="col-sm-6">
[[File:Technology_Trends_-_Low_Code_Application_Development_Gartner_Magic_Quadrant.png|center]]
[[File:Technology_Trends_-_Low_Code_Application_Development_Gartner_Magic_Quadrant.png|center]]
<p class="source">Figure 1 The Forrester Wave: Low-Code Development Platforms for AD&D Professionals, Q1 2019. Used without permission.</p>
<p class="source">Figure 2 : Magic Quadrant de Gartner – Plate-forme d’application d’entreprise comme service à haute productivité. Utilisé sans autorisation.</p>
</div>
</div>
<div class="col-sm-8">
<div class="col-sm-6">
<table class="wikitable hypecycleTable">
<table class="wikitable hypecycleTable">
<tr>
<tr>
</tr>
</tr>
<tr>
<tr>
<td>Challengers</td>
<td>OutSystems</td>
<td>Nouveaux fournisseurs</td>
<td>OutSystems</td>
</tr>
</tr>
<tr>
<tr>
<td>Contenders</td>
<td>Mendix</td>
<td>Fournisseurs concurrents</td>
<td>Mendix</td>
</tr>
</tr>
<tr>
<tr>
<td>Strong Performers</td>
<td>ServiceNow</td>
<td>Fournisseurs performants</td>
<td>ServiceNow</td>
</tr>
</tr>
<tr>
<tr>
<td>Leaders</td>
<td>Microsoft</td>
<td>Chefs de file</td>
<td>Microsoft</td>
</tr>
</tr>
<tr>
<tr>
<td>Stronger current offering</td>
<td>Kintone</td>
<td>Offres actuelles les plus intéressantes</td>
<td>Kintone</td>
</tr>
</tr>
<tr>
<tr>
<td>Weaker current offering</td>
<td>Caspio</td>
<td>Offres actuelles les moins intéressantes</td>
<td>Caspio</td>
</tr>
</tr>
<tr>
<tr>
<td>Weaker strategy</td>
<td>AgilePoint</td>
<td>Stratégie plus faible</td>
<td>AgilePoint</td>
</tr>
</tr>
<tr>
<tr>
<td>Stronger strategy</td>
<td>MatsSoft</td>
<td>Stratégie plus solide</td>
<td>MatsSoft</td>
</tr>
</tr>
<tr>
<tr>
<td>Kony</td>
<td>Bpm’online</td>
<td>Kony</td>
<td>Bpm’online</td>
</tr>
</tr>
<tr>
<tr>
<td>Microsoft</td>
<td>Quick Base</td>
<td>Microsoft</td>
<td>Quick Base</td>
</tr>
</tr>
<tr>
<tr>
<td>Salesforce</td>
<td>TrackVia</td>
<td>Salesforce</td>
<td>TrackVia</td>
</tr>
</tr>
<tr>
<tr>
<td>ServiceNow</td>
<td>Fujitsu</td>
<td>ServiceNow</td>
<td>Fujitsu</td>
</tr>
</tr>
<tr>
<tr>
<td>GeneXus</td>
<td>OrangeScape</td>
<td>GeneXus</td>
<td>OrangeScape</td>
</tr>
</tr>
<tr>
<tr>
<td>Progress Software</td>
<td>Zoho</td>
<td>Progress Software</td>
<td>Zoho</td>
</tr>
</tr>
<tr>
<tr>
<td>WaveMaker</td>
<td>Betty Blocks</td>
<td>WaveMaker</td>
<td>Betty Blocks</td>
</tr>
</tr>
<tr>
<tr>
<td>MatsSoft</td>
<td>Kony</td>
<td>MatsSoft</td>
<td>Kony</td>
</tr>
</tr>
<tr>
<tr>
<td>Thinkwise</td>
<td>Appian</td>
<td>Thinkwise</td>
<td>Appian</td>
</tr>
</tr>
<tr>
<tr>
<td>Skuid</td>
<td>Oracle</td>
<td>Skuid</td>
<td>Oracle</td>
</tr>
</tr>
<tr>
<tr>
<td>Clear Software</td>
<td>Pegasystems</td>
<td>Clear Software</td>
<td>Pegasystems</td>
</tr>
</tr>
</table>
</table>
<div class="container">
<div class="container">
<div class="row">
<div class="row">
<div class="col-sm-4">
<div class="col-sm-6">
[[File:Technology_Trends_-_Low_Code_Application_Development_Top_Goals.png|center]]
[[File:Technology_Trends_-_Low_Code_Application_Development_Top_Goals.png|center]]
<p class="source">Figure 3 Top Goals with Respect to the Digital Experience Provided for Citizens. Used without permission from: Improving Digital Experience for End Users in the Public Sector, IDG Research Services, December 2018.</p>
<p class="source">Figure 3 Top Goals with Respect to the Digital Experience Provided for Citizens. Used without permission from: Improving Digital Experience for End Users in the Public Sector, IDG Research Services, December 2018.</p>
</div>
</div>
<div class="col-sm-8">
<div class="col-sm-6">
<table class="wikitable hypecycleTable">
<table class="wikitable hypecycleTable">
<tr>
<tr>
</tr>
</tr>
<tr>
<tr>
<td>Challengers</td>
<td>Increase the quality of citizen user experience</td>
<td>Nouveaux fournisseurs</td>
<td>Accroître la qualité de l’expérience utilisateur du citoyen</td>
</tr>
</tr>
<tr>
<tr>
<td>Contenders</td>
<td>Lower service delivery costs</td>
<td>Fournisseurs concurrents</td>
<td>Diminuer les coûts de la prestation des services</td>
</tr>
</tr>
<tr>
<tr>
<td>Strong Performers</td>
<td>Improve data security</td>
<td>Fournisseurs performants</td>
<td>Améliorer la sécurité des données</td>
</tr>
</tr>
<tr>
<tr>
<td>Leaders</td>
<td>Provide better access to data and information</td>
<td>Chefs de file</td>
<td>Offrir un meilleur accès aux données et à l’information</td>
</tr>
</tr>
<tr>
<tr>
<td>Stronger current offering</td>
<td>Increase speed of service delivery</td>
<td>Offres actuelles les plus intéressantes</td>
<td>Accroître la rapidité de la prestation des services</td>
</tr>
</tr>
<tr>
<tr>
<td>Weaker current offering</td>
<td>Reduce staff time spent addressing citizen/student requests, questions, complaints</td>
<td>Réduire le temps consacré par le personnel à la résolution des demandes de renseignements, des questions et des plaintes des citoyens et des étudiants</td>
<td>Stratégie plus faible</td>
</tr>
</tr>
<tr>
<tr>
<td>Stronger strategy</td>
<td>Increase usage or programs/generate revenue</td>
<td>Stratégie plus solide</td>
<td>Accroître l’utilisation des programmes et générer des revenus</td>
</tr>
</tr>
<tr>
<tr>
<td>Market presence</td>
<td>Develop user profiles to personalize transactions</td>
<td>Présence sur le marché</td>
<td>Créer des profils d’utilisateurs pour personnaliser les transactions</td>
</tr>
</tr>
</table>
</table>
<li>Most organizations experience some pushback from traditional developers, partly due to skepticism, though often due to defensiveness as more (and cheaper) people become “developers.”</li>
<li>Most organizations experience some pushback from traditional developers, partly due to skepticism, though often due to defensiveness as more (and cheaper) people become “developers.”</li>
<li>Most traditional development environments involve a one-off purchase of the IDE, however, low-code licenses are considerably more complex, often involving per-deployed-app costs. Those costs are sometimes opaque and need to be fully worked through for the ROI analysis.</li>
<li>Most traditional development environments involve a one-off purchase of the IDE, however, low-code licenses are considerably more complex, often involving per-deployed-app costs. Those costs are sometimes opaque and need to be fully worked through for the ROI analysis.</li>
<li>There are several low-code systems to choose from, though the current leaders (which include Mendix, Microsoft and OutSystems) have consistently been ahead of the pack . Which platforms to choose is a challenge that depends heavily on legacy software to be supported, existing deployment platforms, etc. Supporting more than one low-code platform will bring its own challenges.</li>
<li>There are several low-code systems to choose from, though the current leaders (which include Mendix, Microsoft and OutSystems) have consistently been ahead of the pack</p><p class="highlighted inline mw-collapsible-content"> (That is not quite true for Microsoft, which is relatively new to low-code, though their development environments and general platforms are very mature and strategic.)</p><p class="inline">. Which platforms to choose is a challenge that depends heavily on legacy software to be supported, existing deployment platforms, etc. Supporting more than one low-code platform will bring its own challenges.</li>
<li>The proprietary nature of low-code gives a certain level of “lock-in,” preventing SSC from changing vendor or leaving low-code altogether. Vendors usually portray low-code as having no lock-in because C# or Java code is generated, which may be maintained further without low-code. In practice, this is not true for large apps.</li>
<li>The proprietary nature of low-code gives a certain level of “lock-in,” preventing SSC from changing vendor or leaving low-code altogether. Vendors usually portray low-code as having no lock-in because C# or Java code is generated, which may be maintained further without low-code. In practice, this is not true for large apps.</li>
<li>Low-code’s ease (“democratization”) of app development can cause problems for SSC: clients will be tempted to develop on their own if SSC is not fast enough, thereby creating a shadow IT (hidden/skunk works) mentality. If allowed to grow, this will create maintenance issues as well as an existential problem for SSC.</li>
<li>Low-code’s ease (“democratization”) of app development can cause problems for SSC: clients will be tempted to develop on their own if SSC is not fast enough, thereby creating a shadow IT (hidden/skunk works) mentality. If allowed to grow, this will create maintenance issues as well as an existential problem for SSC.</li>
<p>SSC should consider a low-code trial for several reasons: gaining exposure, evaluating low-code tools, and quantifying the ROI (at least for one project). Ideally, all of the leading low-code systems should be evaluated – though the field may be thinned (e.g. to Microsoft PowerApps or OutSystems) based on breadth of the system as well as the match to existing technologies in-use by SSC. During the trial, several aspects should be measured: training cost (which is then translated to amortized training costs as they would be across several projects), amortized licensing costs, elapsed time, client satisfaction, and amortized maintenance costs.</p>
<p>SSC should consider a low-code trial for several reasons: gaining exposure, evaluating low-code tools, and quantifying the ROI (at least for one project). Ideally, all of the leading low-code systems should be evaluated – though the field may be thinned (e.g. to Microsoft PowerApps or OutSystems) based on breadth of the system as well as the match to existing technologies in-use by SSC. During the trial, several aspects should be measured: training cost (which is then translated to amortized training costs as they would be across several projects), amortized licensing costs, elapsed time, client satisfaction, and amortized maintenance costs.</p>
<h2>References</h2>
<ol>
<li>Appian. (2016). <i>[https://www.appian.com/assets/sites/14/2016/12/low-code-guide.pdf Low-Code Guide].</i> Retrieved from appian.com</li>
<li>Azoff, M. (2018, April 13).<i>[https://ovum.informa.com/resources/product-content/ovum-decision-matrix-selecting-an-enterprise-mobile-application-development-platform-201819 Ovum Decision Matrix: Selecting an Enterprise Mobile Application Development Platform, 2018–19].</i> Retrieved from ovum.informa.com</li>
<li>Maio, A. D., & Howard, R. (2018, November 2).<i>[https://www.gartner.com/doc/reprints?id=1-667LEM1&ct=190130&st=sb Introducing the Gartner Digital Government Maturity Model 2.0].</i> Retrieved from gartner.com</li>
<li>Marvin, R. (2018, August 10).<i>[https://www.pcmag.com/roundup/353252/the-best-low-code-development-platforms The Best Low-Code Development Platforms for 2019].</i> Retrieved from pcmag.com</li>
<li>Mendix. (2019, July 4).<i>[https://www.mendix.com/why-developers-should-embrace-low-code/ App dev has evolved: Why developers need to embrace Low-Code].</i> Retrieved from mendix.com</li>
<li>Outsystems. (2019, March 26).<i>[https://www.outsystems.com/1/idg-report-low-code-development-local-government/ Accelerating Digital Government With Low-Code Development].</i> Retrieved from outsystems.com</li>
<li>Revell, M. (2019, February 7).<i>[https://www.outsystems.com/blog/what-is-low-code.html What Is Low-Code?]</i> Retrieved from outsystems.com</li>
<li>Rymer, J. R., Koplowitz, R., Mines, C., Sjoblom, S., & Turley, C. (2019, March 13).<i>[https://reprints.forrester.com/#/assets/2/160/RES144387/reports The Forrester Wave™: Low-Code Development Platforms For AD&D Professionals, Q1 2019].</i> Retrieved from reprints.forrester.com</li>
<li>Vincent, P., Baker, V., Natis, Y., Iijima, K., Driver, M., Dunie, R., . . . Gupta, A. (2018, April 26).<i>[https://www.gartner.com/doc/reprints?id=1-4XVPI4N&ct=180430&st=sb Magic Quadrant for Enterprise High-Productivity Application Platform as a Service].</i> Retrieved from gartner.com</li>
<li>Wikipedia. (2019, July 18).<i>[https://en.wikipedia.org/wiki/Low-code_development_platform Low-code development platform].</i> Retrieved from en.wikipedia.org</li>
</ol>
</div>
</div>
{{#css:
{{#css:
.breadcrumb-table{ margin: auto; }
.breadcrumb-table{ margin: auto; }
.expand{ background-color: rgba(242, 109, 33, 0.2); }
.highlighted{ background-color: rgba(242, 109, 33, 0.2); }
.mw-collapsible-text{ text-align:left; }
.mw-collapsible-text{ text-align:left; }
.inline{ display: inline; }
.inline{ display: inline; }
width: 100%;
width: 100%;
display: table;
display: table;
content: " ";
}
}
.col-sm-8{
.col-sm-1,
.col-sm-2,
.col-sm-3,
.col-sm-4,
.col-sm-5,
.col-sm-6,
.col-sm-7,
.col-sm-8,
.col-sm-9,
.col-sm-10,
.col-sm-11,
.col-sm-12 { float: left; }
.col-sm-4{
.col-sm-1 { width: 8.333333333%; }
.col-sm-2 { width: 16.66666666%%; }
.col-sm-3 { width: 25%; }
}
.col-sm-4 { width: 33.333333333333%; }
.col-sm-5 { width: 41.6666666666%; }
.col-sm-6 { width: 50%; }
.col-sm-7 { width: 58.333333333%; }
.col-sm-8 { width: 66.66666666666%; }
.col-sm-9 { width: 75%; }
.col-sm-10 { width: 83.33333333333%; }
.col-sm-11 { width: 91.6666666666%; }
.col-sm-12 { width: 100%; }
.hypecycleTable{
.hypecycleTable{
}
}
.col-sm-1,
.col-sm-2,
.col-sm-3,
.col-sm-4,
.col-sm-5,
.col-sm-6,
.col-sm-7,
.col-sm-8,
.col-sm-8,
.col-sm-6,
.col-sm-9,
.col-sm-4{
.col-sm-10,
.col-sm-11,
.col-sm-12 { clear: both; display: block; width: 100%; margin: auto; }
div>a>img {
div>a>img {