Categories
Blog

Customers don’t love banks. They love banking apps.

Tech-savvy users are swiping left aggressively and swiping right selectively. No, we are not talking about dating apps. We are talking about how quickly the customers of today are changing their banking preferences. Loyalty is a fickle emotion. As Jeffrey Gitomer says “You don’t earn loyalty in a day. You earn loyalty day-by-day“, by responding to the customer’s needs every single day. Otherwise, they just move on.

How responsive banks are to the changing needs of the customer will now decide their longevity. Or else, it’s a swipe left for sure.

With so much at stake, what can banks do to retain their customer’s loyalty?

Going digital is an obvious answer, but then everyone is doing it. Every bank of repute has a digital face–some, more advanced than others. What spruces up the relationship between the customer and the banking app is the customer journey. It is all about how the relationship started and how it sustains–the qualities that keep the customer engaged, the features that make a banking app sticky. So what are the features in a banking application that entices customers, and how does the WaveMaker low-code platform help?

  • Intuitive interfaces
    Clean and intuitive interfaces that keep screens simple but engaging to use, top-grade UI widgets that help create this clean look should be integrated into the low-code platform that aids this kind of interaction. WaveMaker has a plethora of widgets with diverse themes and styles that can be further customized per customer needs.
  • Account information at a glance
    Accessing account information need not be a cumbersome process involving multiple authentications. Modern banking applications allow their customers to view their account information with just Touch ID or Face ID without having to log in using a password. WaveMaker allows developers to interface with external biometric components by providing customized abstractions over the APIs.
  • Corporate and Personal bank accounts management
    A single app should be able to handle multiple associated accounts, link to third-party offers, offer rewards like cash backs, and provide intelligent and relevant offers. The WaveMaker platform allows the creation of prefabs or reusable software components customized to the banks’ requirements that can be easily composed together to bring in value addition to the application.
  • Virtual smart cards management
    Physical credit cards are passe. Virtual cards are in. Modern banking apps allow the creation of virtual cards within the application within minutes. Customers can transfer funds in and out of the cards and perform transactions all within the context of the application. Virtual card management prefabs within the WaveMaker platform allow developers to just pull in the prefab and customize it according to their requirements with just a few changes.
  • Visualization of data
    Customers should be able to see their information in one place. It is not just what information they see but what inferences that they can draw–spend analysis, expense management, ways to improve credit score–a real-time visual dashboard. WaveMaker facilitates these visualizations where developers can access data from all modern data sources and integrate them with relevant UI abstractions with just a few steps.
  • And……….
    Interlinked payment gateways, QR code scanners, OCRs, loan applications made easy, instant digital KYC, added conditional authentication, currency converters, instant loans, multi-device support, mobile photo bills, wearables and so on.

Though a banking application may not necessarily be composed of all of the above, it should at the very least be provided compatible platforms that enable the development of these features. So the question one may ask is, does WaveMaker as a low-code platform support the integration of these features into a composable banking app?

The answer is a resounding yes!

A developer working on WaveMaker can take two approaches:

One, use the built-in prefabs to quickly conjure up a banking-specific component.
Two, integrate third-party banking components into the application.

This is helped by two factors:

  • One that Wavemaker has an exhaustive repository of reusable components (also an evolving list of customizable banking components)
  • Two, WaveMaker is an API-first development platform that allows the integration of third-party components easily

WaveMaker allows seamless collaboration of ecosystem partners with ease–the foundation of a composable architecture. It helps banks, BaaS players, fintech, and ISVs respond to what customers ask for–modern experiences, intuitive interfaces with stunning visual components, security, smooth onboarding, and device-agnostic feature-rich applications. WaveMaker with its API-first approach, prefabs, support for all major databases, and vault-like security with VeracodeTM certified code has all the qualities to broker a long-lasting partnership with the bank and the customer with agility.

Banks can expand the reuse of legacy core banking, offer services to brands as a BaaS player, or launch greenfield initiatives; with WaveMaker, the possibilities are endless.

So, this time when the user swipes right, banks can swipe right back at them!

*Watch this space for our next article on our banking software components

Categories
Insights

Low-code development and BaaS APIs: is this embedded finance’s hockey stick moment?

By Vikram Srivats, Vice President, WaveMaker

Enough has been said and written about the effect of the pandemic in hyper-accelerating the shift to digital – for enterprises and consumers alike. This is one widely accepted fact we can note and move on from.

The combination of low-code development and BaaS APIs are enabling more companies than ever to add banking services to existing apps and products

However, another rising wave has been afoot for a few years now – something that Bain Capital Ventures (BCV) thinks is far greater than the Internet, Cloud, and Mobile combined (yes, you read that right) – with a projected market value of $3.6 trillion by 2030. BCV heralds this wave as the Fourth Platform: financial services in an embedded (or integrated) form within technology-driven businesses.

Andreesen-Horowitz (a16z) and CB Insights talk about this being the banking industry’s “AWS moment”, with new Banking-as-a-Service (BaaS) players offering all (or parts of) the banking stack as-a-service for a new crop of fintech and tech-driven brands. a16z further predicts that every company will become a fintech company – embedding finance across digital and traditional brands – by leveraging offerings from BaaS providers.

Embedded finance and BaaS are two sides of the same coin. Brands and fintech offer embedded financial services to consumers and businesses while BaaS providers are the suppliers and enablers for those brands and fintech.

Two trends collide to form one massive opportunity

With the pandemic driving a tectonic shift to online, virtual, and instant gratification, embedded finance allows brands and disruptive new financial products to gain and delight customers, increase share-of-wallet and create stickiness. From a customer standpoint, the financial experience is in the moment, contextual and seamless within the brand experience – to the extent that the finance is almost invisible.

For example, think of Apple – which now offers a credit card backed by Goldman Sachs – or Shopify – going above and beyond by offering embedded payments, balance accounts, and loans to aspiring e-commerce businesses. With the likes of Amazon, Google, Doordash, Chime and Affirm, the list of embedded finance and BaaS-powered use cases and players is growing rapidly.

This growth is primarily fueled by a whole slew of capable BaaS players – Synapse, Treasury Prime, Stripe, Marqeta, Bond, Finastra, Railsbank, Solarisbank, Unit, Galileo, BBVA Open Platform, GPS, and many more – offering differentiated and compelling technical and financial propositions. These BaaS players in turn have partnerships with one or more banks and offer APIs (sometimes a single API) for a brand or fintech customer to call and access the offered financial service via the API.

In a way, things have come full circle – from the software powering financial services (core and engagement platforms) at FIs, we now have banking subsumed into software and offered via APIs.

BaaS APIs are becoming the new currency in the world of financial services

With this BaaS revolution going on in the background, the low-code market has grown exponentially, with more than 100 platform providers – with different specializations – competing for market share. 

Microsoft, Mendix, OutSystems, and ServiceNow are some of the leading players while there are specialist challenger firms more focused on specific personas (professional developers, citizen developers, and business process users) and target areas (apps, workflow, automation, analytics, and so on).

To say that low-code adoption was propelled further by the pandemic is an understatement. Whether for businesses urgently wanting to digitally transform or for more advanced corporations, low-code has comfortably hit its stride as a new paradigm in software development.

Now, with over 2,000 fintech launched in 2019, the rise and maturity of BaaS offerings and differentiated embedded finance use cases/opportunities, and a world where APIs rule, developers are now the first customers of the banking and financial services capability stack.

Brands and fintech, banks and third-party software developers, independent software vendors, and system integrators need to find, attract, hire, train, mentor, motivate, manage and drive world-class development teams to deliver business outcomes.

They must do all this in the face of non-trivial challenges:

  • Talent wars in a field of wider opportunities as business lines blur and career options abound for software developers.
  • Walking the fine line between investing to build a truly high-quality product that customers will love, yet balancing cash burn and ROI.
  • Navigate a web of technology choices for every aspect of the tech stack, including most importantly, the BaaS vendor stack itself.
  • Be prepared to execute quickly – and pivot on a dime – to get ahead of the market in an extremely competitive, dynamic, and fast-paced environment.

A breed of developer-friendly, open, API-driven, modern, enterprise-grade low-code platforms could be the answer. Here is how:

  • Serious B2C and B2B2C digital experiences at the speed of change – delivered using visual full-stack development with pre-existing widgets, themes, styles, and layouts – while still playing well with existing assets, best practices, and architectural choices.
  • Significantly cut development (specifically UI) cost by reuse – Lego-like composable experience development by dragging and dropping custom-built, rich multi-API widgets – “prefabs” – that combine powerful functionality, pixel-perfect UI, and data.
  • Democratized and collaborative development – Citizen developers build out experiences based on user journeys and hand them to pros to make apps “enterprise-compliant”; or in a B2B2C context, expert developers build out the core app which is then extended and customized by less-skilled professional services teams.
  • Deliver on tough innovation problems – convert teams to full-stack development, become agnostic to tech stack changes, handle custom UI demands through app lifecycle, move B2B customers to a self-serve model, and more.
  • Peace of mind guaranteed – apps built are performant and secure, the tech stack is modern and future-proof, deploy anywhere without lock-in, generated code is “real” code that can be exported and extended (as an insurance policy), easily available, low-cost skills for writing custom extensions, no price tag for scaling up apps/app objects/app end users and such like.

In 2020, Microsoft cited research predicting that more than 500 million new apps will be built in the next five years, which is more than the total number of apps built in the last 40 years, even as companies struggle to find software developers. According to KPMG, despite the overall market softness in H1 2020, H2 rebounded and saw almost $72 billion in fintech investment (across PE, VC, and M&A deals). Klarna, Revolut, and Chime raised mega rounds north of $500 million each. KPMG goes on to predict that embedded finance will emerge as the *new North Star* in fintech.

Low-code development layered on BaaS APIs may be embedded finance’s hockey stick moment

Embedded fintech and low-code development are massive scale markets in their own right. The next 1,000 or 10,000 fintech, FIs, and brands that deliver embedded financial services will need to be laser-focused on their customers and business to compete and win. Agility, automation, and reuse will underpin composable enterprises and personalized experiences, and modern, powerful low-code platforms already are delivering complex, compelling and contextual experiences for discerning development and business teams globally.

To further explore banking solutions by WaveMaker, please view our exclusive BFSI offerings here.

Or, start a conversation with our expert consultants for solutions to your unique requirements.

Originally published in Fintech Futures

Categories
Blog

WaveMaker v10.8.0 is out!

Team access to artifact repository, improved workflows for artifact publishing, prefabs versioning, and more

WaveMaker 10.8 brings capabilities and features that harness the power of artifacts and prefabs on the WaveMaker low-code platform–especially for teams. Prefabs are custom widgets that can be reused across projects within a team. With this release, the platform consolidates its strength on prebuilt software components by making collaboration across teams faster and easier to manage.

WaveMaker continues to enable enterprise IT teams, ISVs, and all stakeholders to co-create value faster and better with low-code.

Teams - Together and Transparent

Artifacts in Teams

Artifacts are reusable components that can be developed and maintained independently. Various components such as prefabs, project shells, template bundles, and themes come under the umbrella of artifacts on the WaveMaker low-code platform. V10.8 allows the sharing of a central repository of artifacts in teams promoting collaboration between team members.

Team members can view a list of all available artifacts providing clear visibility. Developers have complete access to the repository of available components and are free to choose the artifact version that suits their requirements best. This in turn makes activities such as documentation, maintaining change logs, and version control of artifacts a seamless process.

A new and improved flow

Artifact approval

With 10.8, developers creating and using artifacts across teams and projects can manage their workflows seamlessly. Consider a scenario where a developer publishes an artifact and waits for approval from the team admin. The admin can then review the artifact on the team portal and approve the same, making it accessible for all developers to use or reject it and send it back with changes.

Not just that, the same prefab or artifact can be versioned multiple times with each version visible to all team members. Developers can search and view available prefabs under projects, teams, or system prefabs and import specific versions into the projects.

One component, different forms

Support for specific prefab versions

Different projects can use different versions of the same prefab with a scope for upgrading. Developers can choose versions that suit their requirements with the help of changelogs and get real-time notifications of newer versions. Minor patch updates on prefabs can be published independently using branch support. Development teams can update patches and upgrades seamlessly without disrupting the existing environment and projects.

For ISVs, having access to the latest versions of artifacts is of great value. This allows for both forward and backward compatibility with respect to prefabs with minimum disruption. With every new update, WaveMaker continues to bring developers together, fostering collaboration, and helping them build powerful applications.

To know more about WaveMaker 10.8.0, please read the release notes here.

Categories
Blog

Leveraging low-code for API-driven development

Create, publish and consume APIs effortlessly with WaveMaker low-code platform

Digital transformation is no longer a buzzword. It has become a way of life for enterprises that want to stay in business. In the current post-pandemic era, business maturity is being evaluated in terms of digital maturity. The road to digital adoption has many emerging technologies in force but working silently behind the scenes and aiding this rapid acceleration, is the unseen ‘super glue’ of all business services – Application Programming Interfaces (API). Technically, APIs have been around for two decades at different levels of operability but it is only in recent years that there has been an explosion of sorts in the usage of APIs.

The demand for multichannel experiences and the everything-on-cloud approach has accelerated the use of APIs. Whether it be composable architecture or microservices, APIs enable the kind of business collaborations that were unheard of before. The partnering of transportation services with a bank, retail shops with payment apps, and banks offering investment opportunities, loans, currency transactions, and payment services on an e-commerce platform have all been made possible by the growth of APIs. Similarly, offloading certain business tasks to ecosystem partners and liberating internal services from silos has been fueled by the synergy between APIs.

API-driven development

API-driven development is the practice of designing and building the API contract first and then developing the application around the contract. Also, known as the API-first approach, this paradigm involves the front-end developers building mocks around APIs and creating refined end-user experiences. In parallel, the back-end developers implement the underlying logic of the APIs.

Dedicated test suites are created around these APIs and, in a way, they foster the idea of test-driven development. In an API lifecycle, the API Publisher designs and deploys the API whereas the API Consumer discovers and integrates the APIs. Each of these roles has multiple functions associated with them and those functions define the characteristics of the API.

API Management with WaveMaker low-code platform

WaveMaker is an open standards-based, developer-centric low-code platform built for modern development practices. The platform enables app developers to play the role of an API Publisher and API consumer. The platform has a natively integrated component called the API Designer which is used to ease the process of designing, creating, and consuming APIs.

  • API- first approach: With WaveMaker, a REST API is generated automatically for every service that is imported. These APIs are available for consumption as well as modification through the API designer that can be used for:
  1. Exploring the various APIs generated by the platform
  2. Testing the APIs 
  3. Customizing APIs generated by Java services
  • API GeneratorWaveMaker generates standards-based REST annotations for the above services which can be consumed by API tools for generating documentation using the API generator. The design of these auto-generated REST APIs can be updated further by configuring their description, visibility, method types, and parameter types.
  • Open APIs: The platform generates core REST APIs endpoints using Swagger/Open API compliant contracts for database services, Java services, web services, custom code business logic, or even third-party imports. It also to generates UI functionality for Create, Read, Update, Delete (CRUD) operations for REST APIs which conform to Open API specifications. Integrating an existing REST endpoint with any of the 100+ UI widgets offered by WaveMaker is also straightforward without writing a single line of code. Open API helps WaveMaker apps consume other WaveMaker APIs enabling applications within an enterprise to talk to each other.
  • API Security & TestingSecurity is auto-enabled for an application that can be viewed in the API designer. API security is ensured by securing it with role-based access within the enterprise. API endpoints are also OAuth protected. Once the REST APIs are defined successfully, they can be tested with the “Test” tab. On successful testing, APIs are published along with the applications.
  • Legacy APIs: APIs are invariably REST-based but there remain big remnants of legacy SOAP-based APIs. WaveMaker automatically creates a REST API endpoint for the SOAP services that are imported into an application thus enabling the reuse and modernization of legacy technologies.

WaveMaker offers an API-driven development platform with:

developer-friendly low-code platform abstracts the complexities of API management and provides UI-based connectors to work on the endpoints without having to hand-code. WaveMaker scores high on effortless API creation and management with an API-driven approach and an in-built API designer. The platform’s inbuilt adherence to the rules of the API game and its innate ability to convert any service as an API makes the job of all stakeholders so much easier.

APIs have become an inherent part of software building. Programmableweb (API directory) had a listing of mere 54 APIs in 2005. Today there are close to 24000 APIs listed there, and this is excluding the internal enterprise-level APIs and the ones that haven’t been made discoverable yet. Fuelling this expansion are tools and platforms that help us design, manage, test, produce, and consume APIs. Rapidly, easily and securely.

Categories
Enterprise Application Development

Reaping Angular Advantage with WaveMaker

As web application development evolved, usage of JavaScript skyrocketed. To address the variance in support of JavaScript, HTML across the different browser versions libraries like jQuery evolved to offer a layer of abstraction for the web developers, so that they can just focus on writing their application logic instead of worrying about the vagaries of browser support. Single-page web applications started to become the norm as more code started to be written in JavaScript than ever before. JavaScript has also become the language of choice to deliver applications that run on desktop browsers and mobile phones. So web applications written in JavaScript are now in the run-in environments with huge variations in parameters such as device CPU & memory, network bandwidth, browser support.

Powering this scale of growth needed the emergence of more JavaScript frameworks that provide abstractions over this diversity of hosting environments packaging up the best practices in loading times, memory usage, and responsiveness. There is simply no way to deliver a high-quality user experience without basing application development on top of these quickly evolving JavaScript frameworks such as Angular. Leave it to the smart folks in the Angular team to worry about keeping up with the evolving web application requirements while the application developers’ energies are productively engaged with solving the business problem at hand.

WaveMaker generates Angular code

WaveMaker is the only Rapid application development platform with open-standards-based code generation using Angular & Spring. Our 110+ UI components are implemented as Angular components built into libraries. When the user starts building a page in WaveMaker, the product starts generating Angular code in the background. The generated code imports the UI components user dropped into the page and then wires them up using data binding.

 

The code generated by WaveMaker is fully customizable, allowing developers to write custom business logic in javascript. Using WaveMaker our customers have built a line of business apps, customer-facing portals, and mobile applications in several verticals such as insurance, banking, manufacturing, healthcare, retail, etc.

Build full-stack teams and boost their productivity

WaveMaker offers ready to use and well-tested component library and a visual development environment to drag-n-drop these components to design a page. WaveMaker abstracts away all the Angular concepts like routing, scoping, security (auth guards), i18n, and service integration with REST, SOAP & databases, etc. The developer focuses on building application capabilities like user interface & interaction, representing data with widgets like Forms, Table, Lists or Charts, etc., defining access control for both UI components and APIs.

Mobile-First application development

WaveMaker UI components built using Angular are device responsive and designed to suit mobile-first apps. WaveMaker platform enables hybrid mobile application development, using device-native capabilities through Cordova combined with the power of responsive Angular widgets.

Bring in existing UI components

While WaveMaker has 110+ UI components and this list is ever-growing, we realize that teams may want to build reusable UI components to further decrease the time it takes to build applications in WaveMaker. WaveMaker supports importing reusable JavaScript components that are packaged as Angular.io elements, web components, or jQuery widgets. Using a WaveMaker feature called “prefabs” existing UI components can be imported and these will stay accessible alongside the standard WaveMaker UI components and can be easily dragged and dropped onto the page that is getting developed.

Keep your application on the latest version of Angular

When users develop an app, WaveMaker generates application metadata that does not depend on a specific Angular version. From the metadata the Angular code is generated by the platform, keeping the app agnostic of any specific version of Angular. This means that the app will stay using the latest versions of Angular as WaveMaker rolls out the support for those versions. By simply upgrading WaveMaker versions the application will start reaping the benefits of staying on the latest version of Angular. There is no need to spend time in big stack upgrade projects that consume the productivity of your team.

Build applications that load faster

One of the benefits of Angular is that the framework comes with tools that support very advanced build strategies that reduce your application’s footprint. This is very important to the application’s load time as the amount of JavaScript that is getting downloaded from the cloud uses up critical resources such as network bandwidth, device CPU. Smaller the application footprint, the faster the app loads. When you attempt to deploy the WaveMaker app, we internally use ng build –prod mode with tree shaking enabled so that each page includes only the WaveMaker UI components that it uses and not all of the library. Essentially, the WaveMaker platform takes care of all the build optimizations and keeps the application footprint as optimal as possible to give better performance and first-time load experience.

Easy to deploy onto a CDN

WaveMaker builds which are triggered when the Deploy button is clicked can produce different bundles for frontend, backend code enabling the frontend code to be deployed on a CDN. Each of the resources the page depends on includes a fingerprint that represents the contents of the resource. This means that CDN that is serving static assets can be configured to set cache headers allowing browsers to cache the content and further optimizing the load times for returning users. Because of the content-based fingerprinting incremental releases of the WaveMaker application will only link to newer static assets if there was a change. In most cases, WaveMaker UI components for a page are already in the browser’s cache.

Categories
Insights

Realizing the Benefits of Containers for Rapid Application Delivery

Docker and container technology are well-known in Enterprise today. The simplified view of containers as a miniaturization of VMs seems to yield benefits of portability and faster startup times. But what is less apparent is the benefit they bring to the business. To understand this, we must first look at various scenarios in which the technology can be applied. Just as Java technology applied to IoT or Android is different from that applied to Enterprise software, the benefits realized from any technology, along with its challenges, vary depending upon the context of its application.

In this post, we’ll explore a couple of contexts in which container technology can be applied and how its benefits and challenges differ.

Containers for infrastructure optimization

This is the most common context. Here, containers are adopted by IT as a form of software packaging and distribution. Typically, IT expects to be provided with containers instead of application binaries by the development teams. So containers act as a sort of black box that contains all the software and its dependencies. Developers require to package and deliver a set of container images along with relevant configuration files–that describe how these containers may talk to each other (ports), what storage needs they have (volumes), and so on. From an IT stand-point this creates a homogenous black-box approach to deploying pretty much anything in the Enterprise, and this makes it especially suited to large, data-center scale deployments.

In this condition, the application and adoption of container technology is largely IT-oriented. It favours IT over developers as the latter need to do a lot of heavy-lifting–converting their app binaries and dependencies into container images and pushing them into a container registry. Most container management platforms out there focus on providing the right tools to IT to pull those images from a registry and provision them on a set of machines (physical or virtual). The focus of such platforms is purely on run-time aspects, such as container orchestration, with a very little context of the app or the app stack itself.

The key benefit of approaching container technology in this context is the optimization of infrastructure resource. Platforms like Kubernetes were born out of such a need to optimize infrastructure usage at very large scales (say, millions of containers). However, there are two points of caution. One, this may result in further isolation between IT and developers causing more throw-the-problem-over-the-wall scenarios. No matter how perfect the technology, experience tells us that more de-siloed communication and collaboration is the approach towards hassle-free and rapid delivery of applications in production. Hence, “DevOps”. Two, it is questionable whether all applications are suited to such a black-box hands-off approach between developers and IT. Also, the effectiveness of this approach in real usage remains to be seen.

Containers for rapid application delivery

In this case, application delivery teams adopt containers with the primary goal of speeding up the time-to-market for their apps or products. Using the rapid portability advantages of containers, development and devops engineers put together the app composition, wire together various services/ micro-services–by use of service discovery–and setup configurations for various environments. This context of container usage is more app-focused and less infrastructure-focused (though the resource optimization benefits of containers accrue over time as more apps adopt containers for delivery). Also, the approach is both design-time and run-time focused and favours development and DevOps teams over IT. It seeks to make development teams self-sufficient in getting their apps into the hands of their users.

Few platforms focus on these aspects that provide developers the required tools to automate the generation of container images, service versioning, and configuration for multiple environments of the app. The most important benefits of such platforms are rapid containerization of existing apps, rapid provisioning and configuration, and easy promotion of apps from one environment to another. Orchestration takes care of scalability and high-availability requirements, and these are configured entirely from an application perspective.

The greatest benefit for enterprises using containers for rapid application delivery is time-to-market for their apps rather than infrastructure optimization. As the market for containers matures further, expect to see a shift in focus towards this direction.

Introducing WaveMaker HyScale

Wavemaker HyScale is an app containerization and container management platform that takes the view that an application’s time-to-market is a far more important focus for Enterprise business than infra-resource optimization. The platform is built ground-up with the application in mind and every aspect is designed around the app’s stack, the app’s services, and the app’s configuration. Hence there are very few (if any) aspects of the platform that require users to deal with the underlying container technology aspects. In fact, HyScale makes it very easy for users to adopt the platform–and thereby adopt containers–without even requiring to know Docker, or use any Docker commands or even any kind of build/ deploy YAML configuration files.

HyScale allows development teams to stay focused on the app and become self-servicing at the same time, allowing them to rapidly deploy and iterate over their app.

Contact us to know more about how WaveMaker HyScale can empower your organization to achieve faster time-to-market with containers and without having to re-skill or re-tool you development workflows.

Categories
Insights

Enterprise Digital Transformation

Do not hesitate. Start from your employees.

The term, Enterprise Digital transformation, has been much maligned and misused by everyone from a consultant to a developer to a technology leader.  It has been used to describe anything from creating a website to incorporating data analytics to developing a social media strategy to just plain digitization of old paper records.   

However, a truly transformative enterprise digital experience can be achieved only when everyone in the organization feels the change.   In essence, enterprises should start their enterprise digital transformation process with their employees.

There are lot of ways you can engage your employees, but make sure you have at least accomplished the following three :

  • Emancipate your employees to kindle their innovation nerve, by sharing access to digital assets through APIs
  • Engage your employees, to ideate, collaborate and share ideas
  • Empower your employees, to give shape to their ideas through a low-code app development platform

Emancipate your employees with an API management platform

Enterprise digital assets can be anything from list of all employees to list of all items procured to list of all vacation data to list of all products that the organization sells.  Not all data will be relevant to everyone.  For instance, sharing of payroll compensation data with employees will not be such a great idea.  

Sharing digital assets with external entities to promote additional revenue channel or engage customers and partners to create apps are now ubiquitous among enterprises.  Usually the digital assets are API’fied and shared with the external entities to consume.  An API Management platform is usually deployed to API’fy the digital assets, monetize using plans, and configure security and data governance policies.  Create a set of API access plans for employees and share these APIs with the employees, through a dedicated employee API portal.  

Engage your employees with a collaboration platform

We are in a digital era and having a collaboration platform within an enterprise seems to be a no-brainer.  Still there are many organizations out there with no platform to engage their employees.  There are many platforms like Slack, Yammer for your employees to collaborate and unleash their creativity.  

Engage your employees constantly, asking for their opinions on issues you are facing, announce new customer wins, conduct polls – make them feel interested and that they are wanted.  Listen to your employees, you will find some amazing idea emerging from them.  These new ideas and innovation are going to take your organization to the future.  

Empower your employees with an innovation platform

So, you have unleashed the plethora of enterprise digital assets through the API management platform and started to engage your employees through a collaboration platform.  What next? What if one of your employees has a great idea that he wants to see it materialize as an app?

Organizations should empower their employees with the fastest path from an idea to an app.  They should break the shackles of the employee and remove all hurdles – typically a dependency on technical skills and resources – to create and deploy an app from an idea.   This is what is called an Innovation-Ecosystem.

Invest in a low-code app development platform that encourages employees with no technical skills to get involved, create, and go-live with an app.  Low-code app development platform typically works on a visual development approach with simple drag and drop of UI components, with focus on end-user experience rather than technology.  Low-code platform is the magic pill that is needed to harness the innovation potential within an enterprise.  In short, they are a new age Enterprise Innovation Platforms.   

Some of the world’s biggest business and technology disruptions started internally within an organization.  The most glaring example of that phenomenon is the Amazon AWS, which was piloted and was used as dog-food internally within the organization before it revolutionized the world with its cloud services.  It’s sort of criminal if enterprises don’t harness the innovation potential of their employees, and the best way to enable the innovation ecosystem would be to emancipate, engage and empower your employees.  Try it out for this 2017.

Categories
Insights

The three Rs of enterprise application development: Why should I pick 2?

Enterprises often struggle to strike the right balance for the investment required for various efforts in delivering applications. As businesses become more competitive, largely global, and heavily end user focused, it pushes the boundary of application requirements in order for the apps to be successful.  These requirements are usability, scalability and faster release cycles.

The landscape of application development and delivery has changed a lot in the past few years. Today’s modern applications need to look great, have a robust architecture so it can scale to millions of users, and should be quickly delivered to customers in order to outsmart competition.

The ability to deal with these three requirements has been a constant struggle for any enterprise. In any complex application project, one way or another, we face the immutable law of finite resources: We’re bound by constraints. Good, fast or cheap, we’re told. Pick any two.

This is the classic triple constraint model that you often have to deal with as project leaders. A similar model applies to enterprise application delivery:

Rich UX, Rapid Development or Robust Architecture: pick any two.

As you can see, while all these 3 things are very important for modern applications, they often work against each other. A project that focuses  only on user experience and faster time to market may not have the best robust architecture, while another one that focuses on robust architecture and great user experience may need longer duration to complete. Something has to give, right?

It used to be that businesses depending on the nature of the application could get away by just focusing on two of the above aspects,

  1.  Small and Medium Enterprise: Focus was on Rapid Development and Rich UX
  2.  Non Consumer Business Applications: Focus was on Robust Architecture, Rapid Development
  3.  Businesses that focuses on Robust Architecture and Rich UX always suffered from long lasting development cycles

Should enterprise application delivery always be an exercise in sacrifice. given the demands on IT in today’s Businesses, it has become hard to sacrifice any one of the above. So the question is how do I get to choose all.

Wait.. Hold On, can we get a magical wand that can help us have all the three dimensions of App Delivery. Look no further, modern rapid application development platforms or also referred to as low-code platforms are designed to solve this conundrum.

Take a look at WaveMaker, that specifically addresses the enterprise needs to develop scalable applications, with great user experience out of the box in shorter time frames. Excited, try out a free trial and see how you can now can now cut short development time and still keep intact your enterprise and end user requirements.

 

Categories
Insights

How RAD Platforms Can Move New App Deployment Forward

Rapid application development platforms ­– the low-code and no code tools that have proliferated in the last few years – have given rise to the phenomenon of the citizen developer. A citizen developer is someone who is, or can become, proficient in RAD development, either independently or in support of a professional developer.

In the latter case, creating a new app may involve a tag-team approach in which the pro prepares the components that go into composing an app, and the citizen developer can then develop the app. Such two-pass development is one highlight of select RAD platforms.

The citizen-developer phenomenon has gained a wide following in the past few years, essentially because it enables thin IT teams to reduce their backlog of development projects. Another major reason is that citizen developers, once proficient on a RAD platform, can shelve any older development technologies they may have used.

But even with a wide following, the acceptance of RAD has not spiked in use, but instead has evolved from quick and dirty apps (which were more like prototypes) to nice and final apps (offering a great user experience).

As part of that evolution, a number of use cases for RAD emerged. Arguably, the most popular of those are:

  • Live data forms that are used to create form-based line of business applications with the ability to do CRUD, sorting, caching and loading of data.
  • Prototyping to create working prototypes from application mock-ups to quickly build real-life working prototypes of concepts and wireframes and shorten feedback cycles on application development.
  • Application modernization to allow existing legacy applications to deliver more responsive, modern user experiences while keeping the backend data source and business logic intact.
  • Business dashboards that rely on apps that fetch data from multiple data sources (databases, APIs, custom business logic, files, legacy apps, cloud services, etc.) to populate them and provide access to critical business data.
  • API-driven applications that enable organizations to create greater flexibility in IT application infrastructure by moving away from three-tier applications to smaller, independent microservices-based applications.

RAD platforms are not best suited for developing gaming or other highly interactive apps that use very little data. That would rule out Uber-like apps and gaming apps such as Angry Birds.

RAD is most suitable when the apps are data-driven, often populated from a database system. Pagination of data or memory management (for example, a mobile app that brings in too much data ahead of use may waste data traffic; whereas one that brings in too little could provide poor interactivity) is very tricky particularly when apps need to use AJAX. AJAX is a very common form of programming, for both web and mobile apps, where data is fetched on demand. AJAX applications – also called single-page applications, because data is called into a page without need for a server fetch of a new page – provide a better user experience and are hence preferred.

In addition, low-code platforms are well suited for those applications that are created in Gartner’s Pace Layers model: Systems of Innovation or Systems of Differentiation. Low-code platforms are also suitable for Mode-2 development (the Innovate layer), as defined in Gartner’s Bimodal IT model.

As we see a rampant spread of the consumerization of IT (i.e., corporate apps that look and act like consumer apps), RAD is seeing a new growth phase.

The D in RAD has also been redefined in the new era. Today, the D in RAD refers to both delivery and development. RAD platforms have evolved to cover the entire breadth of application delivery. For instance, some RAD platforms combine a developer cloud to reduce cycle times further (test-as-you-build) and increase productivity. This also makes it simpler to move an app from the developer environment to staging or production (for example, through use of containerization technology).

In short, today’s RAD platforms are nothing like their earlier cousins, although the goal of rapidity still remains.

The challenges of traditional development are not new, nor have there been any substantive improvements in traditional languages that would deliver quantum improvement in time to deployment of new apps – where speed virtually always means corporate cost savings, earlier opportunities for app monetization, or both. That dearth of innovation virtually opened the door for a surge in RAD adoption, whether it resulted from need or opportunity.

Originally published by Vijay Pullur, CEO of WaveMaker, in tmcnet.com

Categories
Insights

Predictions for low-code development using RAD platforms!

It’s that time of the year!!  Predictions for Low-Code Development using RAD Platforms.
First of all wishing everyone a great new year and all the success for your products, services, customers and partners! It is that time of the year, where many in the technology industry spend time penning down predictions on the future of technology and everything revolving around it.  In the past few days, I have read various predictions on technology, tech marketing, sales enablement, tech disruptions, Cyber Security, and the list goes on and on…
I thought to contribute one more prediction to the many, out there.
This blog is my personal take on what 2017 will look for the RAD (Rapid Application Development) and more specifically trends within Applications developed using such an approach. This is based on my experiences working with customers, partners, speaking to folks in this industry and general analysis of the market trends.

Adoption

  • More Enterprises will continue to invest heavily in searching, exploring and concept proofing RAD for their own development needs.
  • RAD will move from experimental discussion to a serious topic of discussion and consideration among architects, development leaders and application influencers within enterprises as a way to increase productivity to develop Applications.
  • While RAD and low-code development platforms came to being to democratize app development and continue to do so, we will see more of professional application developers join the bandwagon of using RAD platforms as a way to develop sophisticated enterprise applications.

Scope of RAD Platforms

  • RAD vendors will evolve from only development to full-fledged development, deployment and application hosting platforms
  •  As professional developers get deeply involved with RAD, they will want to bring in best practices in app development, deployment and DevOps from their vast experiences into application lifecycle. They will push the borders of RAD to increase its scope to include features around DevOps integration, code Branching, automated testing, cloud deployment, real time integration etc.
  • IoT platform integration will emerge as a key use for applications.

Ease of Development
RAD platforms will be expected to provide drag and drop out of box packaged integrations to commonly used services (Payment Gateways, SaaS Platforms, Identity Services, Cloud Services etc). As part of this, API based integration will become a de facto way to develop applications and integrate with internal as well as external systems.        

Ecosystem Play
For enterprises to fully utilize the power of RAD platforms, they will start to coexist RAD with other complementary platforms in the overall App Ecosystem.

  • RAD and API Management Platforms complement each other. These two platforms can feed off each other. RAD can help solve the last mile problem of easy app development for API management platforms. RAD can help create the APIs for App management platforms.
  • With IoT gaining traction, RAD and IoT platforms will gain more traction in this year.
  • SaaS Platforms will use RAD as an effective way to increase developer adoption and ecosystem creation.

Hope this prediction list has been interesting. Let’s see how 2017 pans out for RAD / Low  Code Platforms. While I am not a fortune-teller and do not intend to be one, and guarantee the above predictions, there is one thing I can guarantee, that the ride will be exciting for  RAD platform vendors as well as enterprises that adopt it. So stay tuned and let’s see how this unfolds itself.