News: Glue42 and Eikos Partners to tackle the last mile of the integration journey


New York, NY - Glue42, the company bringing an entirely new desktop experience to buy and sell side firms and retail banks, is partnering with us to resolve the last mile of the integration journey. The aim is to close the disconnect between desktop and back-office needs, which is typically the last hurdle as part of a bank’s digital transformation or employee experience management program.

Many desktop and web apps contain significant amounts of UI and business logic, yet the front end is often ignored. This situation, combined with changing development techniques and new frameworks, means that traditional server-side integration concepts will not help. Simplifying the desktop experience from the data-center is not practicable.

Topics: In The News

Window management on steroids


A new kid on the block has appeared, offering an alternative to desktop operating systems such as OpenFin and electron: welcome Glue42. We had the opportunity to use their toolkit and went to work. Given the breadth and depth of the technology as well as the industry’s struggle with last mile app integration, we started with Glue42’s window management functionality. As we delved into the toolkit, our initial skepticism dissipated.

Topics: Tech Leadership

Micro-frontend architecture and fintech apps: why it’s the way forward



As technology evolves, websites grow increasingly complex and with that complexity comes new challenges. Traditional monolithic architectures are often hard to update quickly. They can become difficult to maintain and scale and must rely on a single stack. We all know this scenario is far from ideal as apps can become quickly outdated this way.

Enter micro frontends. Micro frontends are a way of structuring the UI of a site around a series of independent fragments, extending the benefits of microservice architecture to frontend development. The key to micro frontends is to think about the application as being composed of a collection of features which are owned by independent teams. By breaking up a large monolithic site into smaller pieces, developers can combat many of the problems that arise from added complexity. 

Critical architectural factors / technologies to create killer internal apps


In part two of this series we discussed what technology factors are important, so to close the internal apps series, we’ll discuss the architectural issues and the technology approaches which we think are required to make these efforts successful.

JSCatalyst Tutorial: screen sharing

Here's a situation. You're running JSCatalyst , and you've pulled up a page full of data visualizations and tables. You've customized the filters and styling so it represents exactly the information you need to convey. There are enough different components that the scroll height is too tall for a single screenshot - and then your conversation partner wouldn't get the full interactive experience.

OpenFin Layouts. Our initial assessment.


JSCatalyst tutorial: how to build a dashboard


About JSCatalyst

JSCatalyst is an open-source UI toolkit that supports the development and lifecycle management of high-impact full-stack JavaScript applications. The platform accelerates application development and provides both designers and developers with tools to declaratively build user interfaces that function across all types of devices and browsers.

Topics: Design Thinking

Progressive Web Apps (PWAs): Our Thoughts

As a CTO I am always looking to find technology and approaches that better serve my clients, such as PWA’s (Progressive Web Apps). PWAs formalize what we have been building for our clients for several years now, and that is highly immersive and fluid experiences for the user. They are backed by Google with an initial mobile slant, but, with Chrome desktop, it’s possible to run them on the desktop.  Microsoft is joining the effort and will soon allow PWAs to be run within Microsoft Edge.  Given the number of browsers that are being used today, for PWAs on the desktop to gain sufficient traction, each will need to support hosting PWAs, otherwise the user is limited to two options, Chrome or Edge.

Topics: Tech Leadership

Critical Technology Factors to Creating Killer Internal Apps

In part one of ‘Six Considerations for Building Killer Internal Apps’, we outlined considerations for changing our approach to building and modernizing internal apps. However, putting the business case in place is only the first step.

Six Considerations for Building Killer Internal Apps

Digital transformation is a wide-ranging term. One of the areas of interest is internal applications. However, after years of building external-facing applications, competing with the digital denizens to capture and keep customers through attractive, responsive and easy to use interactions, did we forget about internal citizens?