small_avatar_AdrianR3.png

thumbnail_avatar_AdrianR3.png

avatar_AdrianR3.png

Adrian

GET IN TOUCH

When we were tasked with building a website for Boom SuperSonic, we felt the gravity of the challenge. A groundbreaking aviation start-up, with hundreds of billions of dollars of funding and an aspiration to push the laws of physics to the limit, needed a website that would not disappoint. 

To match their ambition, BoomSupersonic hired a California-based studio, HOO KOO E KOO, to conceptualize and design a powerful web presence. We joined the process to develop a pixel perfect solution.

What is Boom SuperSonic?

From the very beginning Boom Supersonic's ambition has been to allow passengers to travel faster than sound. This dream was a reality in the past but was abruptly ended by Concorde's tragic accident in 2000. 

Boom's flagship airplane - the Overture - was designed to be significantly safer, more efficient and greener than its predecessor. In June 2021, a milestone was reached, as United Airlines announced it ordered the first batch of 15 planes from the manufacturer. 

![ ](\uploads\home-united_2x_3HNaY5HIdoNDhcRs4kYeEc.jpeg)
 Challenges in website development

The designs we received from HOO KOO E KOO stressed the innovative character and seriousness of the project. The site was not intended to be overly complex but had to work impeccably. Think of an airplane manufacturer who cannot engineer its own website...

To reach this goal, our developers used React and Next.js. We paid special attention to the specification we received from designers, spent a considerable amount of time on testing, and brought the website vision to life, just as our client is making their vision a reality. 



small_KHEK_pic01.jpg

thumbnail_KHEK_pic01.jpg

KHEK_pic01.jpg

Boom! How we built a pixel-perfect frontend for a SuperSonic company

Frontend Engineering

UX/UI Design

Research & Discovery

AI For Your Business

Services

Case Studies

Career

About us

Blog

**We all feel that the whole world is spinning faster and faster, not only in terms of technology but also in the way we do business. Here are some bits of predictions on what is likely going to happen in the next few months, brought to you by our CEO, CTO, and CRO.**

### **Adrian Roth** - CEO
> *I am somewhere in between a humanist and a scientific mind. Although I am a philosopher by education, my experience includes management, communication and broadly understood technological issues.*


#### **1. Bringing up the new generation of developers**
If we look at hiring rates and an interest for new developers in Poland and around the world, we can see a gap - depending on who estimates - of 50 thousand up to even 300 thousand programmers in market demand. So we face an industry need on the one hand and a lack of new programmers on the other. Something has to be done, and in the long run a constant race between businesses for new employees that are being taken out from competing companies is not benefiting anyone. 

It leads to high uncertainty in project management, a bigger risk of client churn, and is not good for the IT industry in the long run.

What we can do, aside from looking at closer cooperation with universities and schools, is to start to teach and to create a space for new developers' promotion inside the companies. It is costly and demands a long-term strategy, but this is a price we need to pay to be able to develop and grow our businesses. 

#### **2. New budget ranges and the problem of the pile of money**
Last year, markets were flooded with a huge amount of money and tech businesses got used to ever-larger budgets for digitization (e.g. for IT services and product building). This year we can already see the first signs of the crisis and it surely will make investors less willing to spend money and is going to drive them to make more informed decisions. If we put it together with - sometimes missed - expectations of IT service providers, it may lead to problems for some organizations that are not prepared for shifting from last year’s boom into an upcoming downfall.

#### **3. Instability in Ukraine - as a potential threat for the region**
If a large-scale military conflict in Ukraine (and Belarus) begins, it is possible that companies running IT projects in this region will turn their eyes to other markets, including Poland. If we consider all three topics mentioned, the situation in 2022 can be both a threat or more likely a chance for the Polish tech industry. Of course, a lot depends on whether the money will be spent wisely, and if tech companies are ready to create an environment in which there will be a space for the education of more specialists.

### **Łukasz Roth, CTO**
> *For me, being a CTO means trusting and delegating technology decision-making to the teams.*


#### **4. Efficient remote engineering teams management**
The year 2022 will be a time where remote work of engineers will not be an exception, but a new standard in our industry. What is already routine for members of technical teams, will continue to be a challenge for project managers. Transformation of processes and methods of communication is inevitable, and the market advantage will be achieved by companies that will adapt faster to the new reality and be able to deliver business value to their customers with the same efficiency and the same high quality as before changes.

#### **5. Enterprise jamstack & nocode solutions**
The digital transformation is speeding up, not from year to year, but monthly. Increasing market expectations put pressure on technical teams to deliver solutions at a faster pace. The approach in which the programmer assigns as much responsibility as possible to external services and focuses his work on architecture and business logic fits perfectly into this trend. Headless CMS, headless e-commerce, (Amazon / Google / Azure) Cloud in projects is no longer a surprise. We buy more and more services such as data, identity, and operations in the PaaS model, and we focus on the value unique to the client's needs and ideas. Projects can be validated on the market much faster, and we can witness more specialization in developers' work.

#### **6. Knowledge sharing, soft skills development** 
Any forward-thinking and responsible organization must start investing its time and resources in knowledge transfer. The demand for software engineers in the market is very high, the expectations of professionalism are as high as never before. Nothing happens in a vacuum, if we want to give more responsibility for the tech industry to qualified people, we have to start preparing them now. Market demand lowers standards. If we do not want to let that happen as an industry, this is the time to act. Moreover, the days when a programmer was responsible for code and only code ended a few years ago. Currently, a mature engineer is required to have a whole range of soft skills, and it is also worth taking care of strengthening these qualities in your teams.

### **Greg Motriuk, CRO**
> *I build stable, long-term software development teams in Poland for clients worldwide.*


#### **7. Technological elasticity**
For the next few years, we will witness an increase in the flexibility of experienced engineers in the domain of shifting between technologies. It is true that we live in a world of specialization, but the pace of development of new technologies is so fast that moving from PHP to Node.js should be a new must-have skill-set for every experienced developer. 

Of course, specialization has its advantages, but if you are a mature developer, your background and knowledge is more important, and you should be able to become a senior in new technology within months if you put in enough effort. 

In companies and projects, this kind of skill-set is going to be in bigger demand, so don't be afraid to do that, especially when it is not necessary to always fit in 100%. If you are experienced and flexible, you can start the journey now, and get better with time passing.

#### **8. Ultrafast decision making - startupization of tech industry**
It used to take months to finish an initial part of a deal on software development, and today - in many cases - it takes only a few days. In the blink of an eye, your potential development team can sail to another project - that is how much good coding skills are in demand on the market. And companies (clients) started to realize that. 

The entire industry is going through a "startupization" phase, and it is very important to have a partner who combines business and tech maturity with the speed and flexibility of a startup. In the past, if you got something immediately, it wasn't of good quality. 

Now you have to be precise and fast. Luckily the whole tech industry got more mature and experienced, so it is easier to find a good fit for new challenging projects. 



small_Blog_artykul_Adrian_Lukasz_Grzegorz_prediction_cover_high.png

thumbnail_Blog_artykul_Adrian_Lukasz_Grzegorz_prediction_cover_high.png

Blog_artykul_Adrian_Lukasz_Grzegorz_prediction_cover_high.png

A Bit of noise in the predictions about the tech scene at the beginning of 2022

When I talk to CTOs, I often recommend React.js, which might come across as biased since I work for a company that uses it on a daily basis. However, I made a conscious decision to work in an environment that emphasizes React.js and have been actively encouraging its further adoption within the company. I firmly believe in technology and wouldn't work in an environment that doesn't align with my beliefs, which are outlined below.  React.js is undoubtedly the most widespread, popular, and sought-after frontend technology within the software development community. This alone should be reason enough to make it your go-to framework for frontend development. However, let's delve deeper and explore other reasons supporting this assertion.

#### **Why choosing the right frontend framework matters**
When embarking on a new project or updating an existing application, one of the most crucial decisions to make is the choice of frontend technology. This decision is critical because it has long-term implications for your product and work. In my experience, I have seen several products struggle because of poor past technology choices. Selecting the appropriate frontend technology is a daunting task since it affects not only what the technology does and how it functions but also who can operate with it and what other tools can enhance and augment it.

#### **The pragmatic case for React.js**
The React.js community is massive and its popularity is evident from various statistics. For instance, a search on LinkedIn reveals that over one million people worldwide have mentioned React.js in their profile, indicating some level of experience or interest in the technology. This is significantly more than any other frontend framework.  

The widespread popularity of React.js has two important implications. Firstly, it is relatively easier to find developers with React.js experience than with expertise in any other framework. Secondly, due to the high demand for React.js talent, there is significant competition among employers to hire them.  

At first glance, it may seem like these two facts offset each other when it comes to hiring. Although there are more candidates, there are also more job openings, which should balance the job market. However, the concept of liquidity comes into play, much like in the stock market or altcoin market. The more developers with specific skills that are available, the more likely they are to seek out new opportunities, making it easier to hire.  When considering the long-term perspective, the size and liquidity of the React.js community play a crucial role for both you and your HR team.

![ ](\uploads\Blog_artykul_Grzegorz_React.js_blog_01_1pVcCpqFPKCNby6LpN9XI1.png)
#### **Net talent flows to frameworks**
It's important to remember that today's statistics may not reflect tomorrow's. It's also essential to consider the dynamic nature of people changing their expectations and enhancing their skills. One significant realization I've had over the past few years is that no one wants to switch from React.js or Vue.js to Angular. However, switching in the opposite direction is relatively common.  

For example, a skilled Angular developer with a good understanding of project work, methodologies, and business needs may decide to make a career move and explore a new framework. They could take a React.js course, work on some TypeScript projects in their free time, and be ready for a new challenge in a React.js team within a few months.  

This scenario almost never occurs in the opposite direction. As a result, if you start a project in Angular today, you are more likely to lose your developers to React projects than vice versa.

#### **Avoiding hypes**
Every once in a while, we witness a hype around a particular technology. I remember the sudden rise of Vue.js around 5 years ago. Many developers were attracted to it, mainly because of its ease of use. I talked to several Angular developers and backend engineers who were interested in trying it out. CTOs also wanted to experiment and started their projects in Vue.js. It was an exciting time with good energy, and it was an opportunity for junior developers to become proficient in a particular framework quickly.  

However, as of early 2023, the hype has largely dissipated. Although the technology is still in use, being developed and improved, it hasn't caught up with React.js by any means. I can see some companies now stuck with Vue.js. Although it is easy to use and gets the job done, the talent pool for Vue.js projects is relatively limited.  

(It's also important to note that Vue.js is not very scalable. If your app is likely to grow, you may find it cumbersome to use this framework.)

#### **The case for mobile apps**
If you plan to turn your web app into a mobile app, React is an ideal option. You can use your existing React team to build a cross-platform app in React Native. This approach saves you from having to allocate additional resources and performing the same work twice for iOS and Android. It also maintains the cohesion of your team and makes it easier for developers to switch contexts, ultimately reducing the costs of maintenance.  

In my opinion, an experienced React.js web developer can build a mobile app relatively quickly, even if they lack prior mobile development experience.

#### **Summary**
Choosing the right frontend technology is critical for any project's success, and I recommend React.js due to its widespread popularity, large community, and ease of finding talent. The size and liquidity of the React.js community play a crucial role in both hiring and long-term maintenance. While hyped technologies may be attractive, it is essential to consider their scalability and talent pool before choosing them. React.js is also an ideal option for developing mobile apps, as an existing React team can easily build a cross-platform app in React Native, reducing costs and increasing team cohesion.




small_Blog_artykul_Grzegorz_React.js_blog_cover_high.png

thumbnail_Blog_artykul_Grzegorz_React.js_blog_cover_high.png

Blog_artykul_Grzegorz_React.js_blog_cover_high.png

Why do I recommend React.js as a frontend technology to CTOs?