New face for a major bank — the project which started the Roll!

Client Type: Enterprise

Client Location: Hungary

Industry: Finance, Banking

Tech: Large scale Angular frontend with NgRx and Redux

Year: 2018

Dev Team size: 5 FE, 1 PM, 1.5 QA

This one goes way back. This is actually kind of the origin story for Rollout IT.

It’s the summer of 2018, and one of the biggest commercial banks in Hungary, Erste, had their webbank redesign underway. This was the time of the famous PSD2, the new Payment Services Directive of the EU coming alive, which has been aimed at making 3rd party integrations easier, so fintech startups can create better services for the customers, faster.

Since this required a major frontend overhaul anyway, Erste decided to redesign the personal daily banking platform.

Our founder, Balázs with one of his other senior developers joined the dev team soon after Rollout IT was officially founded. This was the first official occasion of Rollout IT contractors joining a client’s team to improve the development process, help other frontend engineers get up to speed, and ensure that the quality of the development is generally on a high level.

Balázs had a strong vision about how to provide optimal circumstances for IT developers, including pricing, mood, vibe and the project details. He successfully recruited others while he has been working as a senior developer, and had proof that he is able to create good matches, where clients and professionals are both satisfied. Also, by this time Balázs realized that his network is very valuable. (BlackWolf already reached out to him even earlier — you can read more about the Hong Kong mobile game developer project over here.)

This bank project offered the momentum to make the plunge and served as a starting block for Rollout IT. Balázs now wanted to create at least ten of these high quality matches a year, and it all started here.

The key highlights of this project have been the rigorous testing protocols, and the advanced state management in Angular, which enabled you to go back to any state of the code you wanted to work on, even if you refreshed your window.

We really pushed the envelope with frontend modularity, building several independent NPM libraries.

Balázs contributed to several challenging modules, including the advanced page routing, the currency transaction form (with advanced frontend validation) and the so-called ‘yellow cheque’ transactions, when users initiate payments based on the pieces of printed papers that are sent to them, typically from utilities — interesting relics in Hungarian banking. (Most of these have actually been paid in cash at Post Offices, up until Covid hit, and pushed local social fintech adoption over to this side of the digital revolution.)

It was also key to navigate SEPA, and other transaction formats, making it clear for the end-user which one is about to happen.

Although the front end team worked with an already prepared design, the management was ready to consider suggestions about UX.

The project has been an early example of a rough-around-the-edges, somewhat stressful deployment, with tough deadlines. Lots of occasional consultations and high flexibility was required — Balázs remembers working at weird hours on the weekend, sometimes doing classic 3-day ‘hackathon-type’ extreme development together with the other devs, late into the night, with pizza and Coke, just like in the college years. It does have a fun factor, but TBH, at that time, Balazs would have rather skipped theseif he had the chance.

One thing that we learned from this project is client evaluation, a simple table with several aspects rated 1–10. There are a lot of these, from familiarity with the team, clarity about the roadmap and special demands from the management, longevity, and other factors. This is a form of risk management which is the part of the preparation phase for each Rollout project ever since.

The Rollout team has been able to successfully improve the development process, taking care of code reviews, and replacing the imperative code with a more functional/reactive approach. We helped produce a bug-free and easy-to-maintain frontend solution for a major bank, on time, serving as a good starting ground for our future hunts.

You keep your softwares always up-to-date, right? Be informed about the IT & Remote work news and click on the link: https://email.rolloutit.net

Book a call or write to us

Or

Send email

By clicking on ‘Send message’, you authorize RolloutIT to utilize the provided information for contacting purposes. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

According to the Cloud Native Computing Foundation (CNCF), Cloud-Native adoption has soared in recent years, with over 5.6 million developers using Kubernetes alone as of 2021. Leading companies like Netflix, Spotify, and Airbnb have used cloud-native approaches to power their global operations. Just moving to the cloud isn't enough. True success in cloud-native development comes from rethinking how software is built from the ground up. That means embracing flexible architectures, breaking apps into smaller parts that can be deployed independently, automating as much as possible, and focusing on continuous improvement. It's not about using the cloud. It's about using the cloud well.
Did you know that software bugs cost the global economy around $2 trillion annually in the US in 2020? The consequences of defective software range from lost revenue to security breaches and system failures. As businesses scale and products grow more complex, ensuring software quality at every stage becomes a mission-critical task. This is where automated testing toolkits play an important role in maintaining reliability and efficiency. In a world where technology is evolving rapidly, relying solely on manual testing is no longer practical for enterprises that need speed, accuracy, and reliability. Automated testing helps organizations deliver high-quality software while making better use of their resources. Let’s dive into how these toolkits improve quality and efficiency at different stages of software development.
Vibe Coding is the process of developing AI-driven applications in a flow-based, intuitive manner, where developers build prompts, logic, and workflows rapidly, often without writing traditional code. This approach emphasizes creativity, flexibility, and speed, allowing teams to iterate quickly without being constrained by traditional development lifecycles. Focuses on rapid iteration, natural language, and modular building blocks. Popular in environments using LLMs, chatbots, and generative AI products. Empowers non-traditional developers (project managers, designers, analysts) to prototype AI features. Encourages exploration and experimentation with model capabilities. Lowers the barrier to entry for creating intelligent systems.
Many enterprises struggle with outdated systems that don’t work well together. As businesses grow, they add new software and tools, but without a solid integration strategy, these systems become disconnected and difficult to manage. Traditional development often treats APIs as an afterthought, leading to slow development, high maintenance costs, and limited flexibility. API-first development takes a different approach. Instead of building software first and figuring out integrations later, it starts with designing APIs as the foundation. This ensures that all systems, whether internal tools, customer applications, or third-party platforms, can connect smoothly from the beginning. The result? Faster development, easier system upgrades, and a more scalable, future-ready architecture.
By 2025, the mobile learning market is expected to reach around $94.93 billion and is projected to grow to $287.17 billion by 2030, with an annual growth rate of 24.78%. With smartphones becoming more widely accessible, mobile learning (m-learning) has become an essential part of modern education.  This rapid growth reflects a shift in how people access education, making learning more flexible, interactive, and personalized. Whether it's students looking for supplementary resources, professionals upskilling on the go, or educators seeking innovative teaching tools, mobile learning apps have revolutionized the way knowledge is shared and consumed. As technology continues to evolve, the demand for well-designed and engaging educational apps is higher than ever, shaping the future of learning across all age groups.
By 2025, the mobile learning market is expected to reach around $94.93 billion and is projected to grow to $287.17 billion by 2030, with an annual growth rate of 24.78%. With smartphones becoming more widely accessible, mobile learning (m-learning) has become an essential part of modern education.  This rapid growth reflects a shift in how people access education, making learning more flexible, interactive, and personalized. Whether it's students looking for supplementary resources, professionals upskilling on the go, or educators seeking innovative teaching tools, mobile learning apps have revolutionized the way knowledge is shared and consumed. As technology continues to evolve, the demand for well-designed and engaging educational apps is higher than ever, shaping the future of learning across all age groups.