Categories
Blockchain Entrepreneurship Finance Financial Services Other Supply Chain Technology

How to leverage distributed ledger technology in corporate platforms

In the modern-day digital landscape, consortia and corporate platforms face numerous challenges. These include managing complexity, enhancing collaboration, and improving transparency. This article focuses on addressing them using distributed ledger technology (DLT). Power relations, coopetition within consortia, data security, and privacy in decentralized architectures will be the topic of examination.

How to leverage distributed ledger technology in corporate platforms and consortia

Table of contents:

  1. Modern-day application of blockchain
  2. How blockchain can address challenges faced by consortia
  3. Interactions in corporate platforms – a four-phase trajectory
  4. Conditions for a Successful distributed ledger technology Project
  5. Things can go wrong with blockchain
  6. Our distributed ledger technology business case: HLB Global
  7. About this article
  8. About Agnieszka Hołownia-Niedzielska

Modern-day application of blockchain

Distributed Ledger Technology has wide uses. Sectors like settlements and supply chain management continue to leverage it. Logistics use blockchain to track production and delivery processes, prevent food fraud, and verify product origin. It also helps verify transportation conditions, validate expiry dates, and confirm eco-certificates.

How blockchain can address challenges faced by consortia

Operating across companies requires considerations around cost division, compromising needs, and managing relationships without a chain of command. Despite many unknowns that characterize building and organizing consortia, the business case that stakeholders want to work on remains the same. They will be looking for similar benefits. That’s why creating a list of benefits and presenting them to internal stakeholders is important. This shift could have significant implications for all workers. It can lead to increased automation, greater independence from a central unit, and higher accountability. With a more process-oriented approach, organizations can expect better-structured processes, but also better data quality. This could lead to less confusion and more organized cross-company systems.

Ecosystems based on DLT, blockchain, or other decentralized architectures are maturing. More companies now look beyond innovation and publicity. Instead, they focus on tangible business cases. Use cases of these consortia are likely to impact workers not directly involved in software development and tech, such as those in accounting and settlements. By automating repetitive tasks, these technologies allow specialists to focus on expert tasks, reducing mistakes and streamlining processes.

The power within blockchain consortia is distributed differently from that of large centralized platform providers. Blockchain implementation operates independently of the organizational or legal framework. However, its decentralized nature means that each participant owns a full copy of the data, rather than a single central unit that has to be monitored or widely trusted.

Interactions in corporate platforms – a four-phase trajectory

The interaction between various companies involved in such platform projects always has specific characteristics, but it could be streamlined into a four-phase course.

The first phase involves innovators, often CIOs driven by personal interest, who identify a persistent problem. It could be resolved by standardizing the process across companies with blockchain technology.

Later, the initiating company experiencing the issue reaches out to interested parties in other business units. This usually happens after many companies have dealt with the same problem for years.

In the third phase of the process, business owners from one or more companies work together. Occasionally, the tech and legal departments also get involved. Usually, the ones in control of the project consult internally with multiple stakeholders. They then work on a solution acceptable to all businesses.

Finally, the proposed solution is built into a Minimum Viable Product (MVP) or Proof of Concept (PoC) version. It’s then beta-tested, feedback is collected, and the solution gains momentum. Some companies might wish to join only as participants, while the majority prefers to join as nodes to own their copy of data.

Conditions for a Successful distributed ledger technology Project

Maintaining relationships within DLT consortia requires some vital work. Mainly, it’s a key to managing tasks well and organizing things, keeping people on different levels informed. Those managing consortia projects need to consider differences between participants and the number of departments and workers engaged. It’s crucial to understand that processes and roles may differ. As a consequence, the people engaged in the project may change. Depending on the consortium’s participants, the structure of the internal process can also vary.  

Also, although blockchain communication is secure, establishing connections between nodes built in different organizations requires careful consideration of IT policies. Some of them may need adjustments. The team may modify the project’s technical side according to needs. In an ideal scenario, all participants have their node, transforming IT solution consumers into “vendors”.

Gathering feedback regularly is also a success factor. Feedback from early adopters – a group of pilot companies – plays a vital role, especially during usability tests. What’s important to note is that this work isn’t done when the first version of the solution is in operation. Collecting lessons learned after the MVP phase is a method to implement agile adjustments successfully. 

Interested in validating your blockchain project idea? Check out our article:
6 Easy Steps to Verify a Blockchain Project

Things can go wrong with blockchain

However, not all blockchain projects succeed. Some fail because they don’t grow big enough, so they don’t get their momentum. Some people treat consortia projects as internal, resulting in a lack of external communication and adaptability. This creates a restrictive ‘our way is the only way’ mentality. Moreover, implementing change always presents a challenge.

Despite some disappointments, distributed ledger technology consortia and structures keep offering benefits. This could be savings, or utility (paying more but gaining a single, independent source of truth). Developers build these structures in an agile manner, adding new participants and features, and planning for the next steps in the decentralization process. The key is to ensure that end-users actively use these projects; they don’t remain just as ideas hidden in a drawer.

Our distributed ledger technology business case: HLB Global

It’s time to analyze a real-world application, a case study of HLB Global. HLB is a global network of independent advisory and accounting firms. They have independent branches across 157 countries with more than 38 000 professionals, combining local expertise and global capabilities.

Espeo Software created a decentralized system to let members interact with each other more easily. HLB wanted to standardize and clarify its referral processes. They wanted everyone to play by the same rules enforced by the system. With the ability to add new referrals in place via the existing SharePoint interface, it’s now easier for everyone to manage their tasks. To track deal statuses, data is gathered from various sources like project orders, invoices, and payments. We had to build trust into the solution.

We used Hyperledger Fabric, a private blockchain network, as the solution. Users within this network operate in a transparent and secure environment. The system tracks and permanently records every action, ensuring it’s tamper-proof. The permissioned nature of HLF allows only authorized participants to gain access, maintaining the integrity and confidentiality of the blockchain network.

The HLF blockchain network now stores the data. It serves as the one source of truth with immutable data history. We also automated status changes that follow the execution of chain code tasks.

About this article

Espeo Software’s Solutions Consultant, Agnieszka Hołownia-Niedzielska, was invited by Prof. Dr. Ulrich Klüh to share her expertise on a Coopetition in Corporate Platforms project. The Darmstadt Business School conducts the research project, with funding from the Hans Böckler Foundation.

About Agnieszka Hołownia-Niedzielska:

Agnieszka Hołownia-Niedzielska is a Senior Solutions Consultant at Espeo Software. She has over a decade of experience in FinTech and RegTech product development and project management. Having been a business owner herself, she brings unique insights into business and technical analysis across various project sizes. She acquired Blockchain for Business Professional certification.

Categories
Blockchain Financial Services Newsroom Supply Chain

Darmstadt Business School Interviews Espeo DLT Expert

Consortia and corporate platforms face numerous challenges, including managing complexity, enhancing collaboration, and improving transparency. Espeo Software is pleased to announce that its Solutions Consultant, Agnieszka Hołownia-Niedzielska, to contribute her expertise in a research project on Coopetition in Corporate Platforms. The Darmstadt Business School, under the leadership of Prof. Dr. Ulrich Klüh, conducts the study and he also handles the interview. The project, funded by the Hans Böckler Foundation, explores the challenges and solutions of consortia and corporate platforms.

Hołownia-Niedzielska’s interview focuses on how Distributed Ledger Technology (DLT) can help address the challenges consortia and corporate platforms face. She analyzes various aspects and implications of decentralized architectures.

“It’s crucial to emphasize that DLT continues to mature and is no longer merely an innovation. Companies are starting to realize the tangible business benefits it provides,” says Hołownia-Niedzielska. 

According to Hołownia-Niedzielska, success in DLT projects starts with problem identification. This is followed by the second phase, where the needs of interested parties are gathered. The third phase involves collaborative work across companies to create solutions. Lastly, a Minimum Viable Product (MVP) or a Proof of Concept (PoC) is developed. An article with the entire interview is now available as a blog post on our website. 

Be the first to read the article – now on our blog:
How to leverage distributed ledger technology in corporate platforms

Espeo Software demonstrates the tangible benefits of DLT through its successful case study with HLB Global, a network of advisory and accounting firms spanning 157 countries. We developed a decentralized system using the Hyperledger Fabric private blockchain network to enhance transparency in HLB’s referral processes. This solution allows all members to interact seamlessly, with built-in trust and accurate tracking for every action, making the network tamper-proof.

We thank Prof. Dr Ulrich Klüh and Darmstadt Business School for recognizing our expertise in the field of DLT. This technology can become essential to how consortia and corporate platforms operate. DLT can lead to streamlined processes and better data quality by offering security and accountability. 

About Agnieszka Hołownia-Niedzielska:

Agnieszka Hołownia-Niedzielska is a Senior Solutions Consultant at Espeo Software. She has over a decade of experience in FinTech and RegTech product development and project management. Having been a business owner herself, she brings unique insights into business and technical analysis across various project sizes. She acquired Blockchain for Business Professional certification.

About Espeo Software:

Espeo Software has been helping companies develop and implement innovative fintech solutions since 2008. By leveraging our expertise in blockchain, online payments, and other related areas, our clients can invent and create cutting-edge solutions and services that help them stay at the forefront of innovation. 

Categories
Software Technology

[PL] Organizujemy Coding.fest 2.0 w Poznaniu!

Już 22 czerwca (czwartek) spotkamy się w biurze Espeo Software by porozmawiać nt. “Narzędzia AI, a praca programisty”. Na uczestników będą czekały merytoryczne prezentacje przygotowane przez ekspertów z technologii mobilnych, programowania backend oraz programowania frontend. Jedna z prelekcji będzie niespodzianką – a speaker zostanie wyłoniony w drodze konkursu, o którym więcej informacji znajdziesz w dalszej części artykułu.

To doskonała okazja do networkingu z innymi specjalistami, a to wszystko w luźnej festiwalowej atmosferze, gdzie nie zabraknie pizzy, pysznych przekąsek i napojów.

Coding.fest 2.0 #Poznan

Temat: Narzędzia AI, a praca programisty

Data: 22 czerwca (czwartek)

Godzina: 18:00

Miejsce: Espeo Software, ul. Baraniaka 6, 61-131 Poznań

Zapisy: meetup.com

Udział: bezpłatny

Czy to wydarzenie dla mnie?

Programujesz i interesujesz się najnowszymi rozwiązaniami, które mogą ułatwić Ci pracę? Chcesz dowiedzieć się więcej na temat narzędzi AI? A może chcesz podyskutować na ten temat w gronie innych specjalistów? Być może wierzysz w siłę networkingu i chcesz spotkać się ze innymi programistami w Poznaniu by poznać się i wymienić doświadczeniami? Doskonale się składa! Wygląda na to że Coding.fest 2.0 jest właśnie dla Ciebie!

Program wydarzenia

Zaczynamy o godzinie 18:00. Merytoryczna część wydarzenia obejmuje 3 prezentacje. Czas przewidziany na tę część meetup’u to około 90- min. W ramach prezentacji możesz także spodziewać się konkursów dla widowni! Liczymy na Twoje zaangażowanie dyskusję. W trakcie dla gości dostępne będą przekąski i napoje. Po części merytorycznej odbędzie się integracja przy świeżej pizzy. Pamiętaj żeby zapisać się do udziału w wydarzeniu TUTAJ.

Konkurs na wystąpienie

Masz pomysł na temat, który jest związany z AI i programowaniem i chcesz o tym podyskutować? Świetnie się składa! Do naszego składa chcemy zaprosić spikera, który zostanie wyłoniony w ramach konkursu.

Zwycięzca zostanie zaproszony na wydarzenie jako mówca, a dodatkowo otrzyma za swoje wystąpienie nagrodę w postaci 1500 złotych.

Co trzeba zrobić?

W konkursie mogą brać udział wyłącznie osoby pełnoletnie. Należy przygotować krótką prezentacje o tym, co chcesz przedstawić na wydarzeniu. Prezentacja ta powinna być przygotowana w formie wypowiedzi wideo i trwać maksymalnie 90 s (1.5 min).

Zgłoszenie konkursowe

Zgłoszenie należy wysłać mailem zatytułowanym “Konkurs Coding.fest 2.0” na adres: eb@espeo.eu. Można przesyłać je do końca dnia w niedzielę 18 czerwca. Zgłoszenie powinno zawierać twoje dane personale: imię, nazwisko, datę urodzenia, e-mail oraz numer telefonu. Załączony film powinien być w formacie MP4. Przesłanie zgłoszenia jest równoznaczne ze zgodą na przetwarzanie danych osobowych na potrzeby przeprowadzenia i rozstrzygnięcia konkursu.

Wyniki konkursu

Komisja konkursowa złożona z pozostałych prelegentów wybierze zwycięzce w poniedziałek 19 czerwca. Wtedy wszyscy uczestnicy zostaną poinformowani o wynikach. Zwycięzca otrzyma zaproszenie na wydarzenie i wsparcie w przygotowaniu prezentacji na wydarzeniu (przewidywany czas tej prezentacji to 20 – 30 min). Po wystąpieniu zwycięzca otrzyma nagrodę w wysokości 1500 złotych! Powodzenia!

Dołącz do Coding.fest 2.0 w Poznaniu i do zobaczenia wkrótce!

Categories
Design Software

The evolution of Material Design. From Material Design to Material You.

Introduction to Material Design

During the journey of every Android Developer, we have observed various Material Design language rules. We started with the first guidelines of Material Design in 2014. Then we acknowledged the set of updates to the language in Material 2 in 2018. Finally, we have seen the major changes in the newest version of Material Design called Material You (Material 3) in 2021. I will introduce these changes through the years from the Android Developer’s perspective and describe the most valuable changes and new things in Material 3. Let’s begin!

We will go through the following issues:

Versioning of Material Design

Material design is a design language (scheme or style that guides the product design). There were 3 major versions of this language.

Material 1

Google introduced the first version of Google Material Design in 2014. The primary purpose of creating this language was to combine principles of good design with technical and scientific innovation. It allowed the unifying design of Google applications. What else, developers can exclude basic components with Google’s material components API.

Source: https://en.wikipedia.org/wiki/Material_Design

Material 2

The next step was Material 2 (Material Theme), introduced in 2018 as an update of Material 1. The language went through some cosmetic changes to highlight the components even more.

The main differences between Material 1 and Material 2 are:

  • new font — Google Sans,
  •  more white spaces,
  •  rounded corners,
  •  colorful icons, and so on.

The video below is a great example showing the migration from Material 1 to Material 2.

Source: ‘Google Material Design 2.0’, youtube.com, uploaded by mobileCTRL, July 24, 2018

Material 3

Material 3, also known as Material You, is the newest version of Material Design. The two previous versions were strictly standardized. Otherwise, Material 3 focuses on user-oriented personalization. The newest version of the language introduced many updates. Some of them are listed below: 

  • dynamic colors based on the user’s wallpaper,
  • different shapes,
  • new typography,
  • changed components (for example bigger buttons)
Source: ‘Android 12 Official Release – What We Waited For!’, youtube.com, uploaded by In Depth Tech Reviews, October 20, 2021

I believe that James Williams explains very well the changes between Material 2 and Material 3 in the article ‘Migrating to Material Design 3′ (source: Material Design Blog, uploaded at October 27, 2021).

Let’s dig deeper into the major features of Material 3.

Characteristics of Material 3

Dynamic colors

Material You focuses on a variety of different colors and shapes. The colors are fully customizable. On the contrary, with material 2, more apps look similar due to strict standards.

Source: ‘Material Design’, material.io, link: https://m3.material.io/foundations/customization, January, 2023

The dynamic colors allow the app to match the system color preferences. As you can see in the example above, the colors in the app change every time users change the wallpaper.

Shapes

Source: ‘Material Design’, material.io, link: https://m3.material.io/components/widgets, January, 2023

Material You is based on a variety of shapes. You can distinguish different ones used on one screen and even the 7-level shape scale based on the roundedness of the component corners.

Source: ‘Material Design’, material.io, link: https://m3.material.io/styles/shape/overview, January, 2023

Material Icons

Also, Google has updated the icons to Material Icons, which can have slightly different versions. The symbols are easily customizable, and an updated version is available on the Google icon’s page.

Source: ‘Material Design’, material.io, 1. Outlined 2. Rounded 3. Sharp; link: https://m3.material.io/styles/icons/overview, January, 2023
Material Icons 1. Outlined 2. Rounded 3. Sharp;

Topography

The Material 3 typography went through simplification. As a result, from the 6 Headline variations, currently (Jan 2022), we have fewer variants for each classification (Small, Medium, Large).

Source: ‘Material Design’, material.io, link: https://material.io/blog/migrating-material-3, January, 2023

Design material components: Material 3

Buttons

Now, the buttons are rounded. Also, they are a bit higher than in Material 2.

Source: ‘Material Design’, material.io, link: https://m3.material.io/components/buttons/overview, January 2023

Floating Action Buttons

The Action Buttons in Android can be classified as Floating Action Buttons (FAB) or Extended Floating Action Buttons. FAB is a circular button that triggers the primary action in the UI apps. Extended Floating Action Button is the class with the Material Components library in Android. Concluding, it looks more rectangular now.

Source: ‘Material Design’, material.io, link: https://m3.material.io/components/extended-fab/overview, January, 2023

Switches

In Material 3, thumbs are not exceeding the switch track. Even more, there is a space between the thumb and the track.

Source: https://m3.material.io/components/switch/overview

Top App Bar

The Top App Bar and the status bar (displaying the battery and the network icons) now have the same color. Also, there is less contrast between the app bar and the content below. 

Source: ‘Material Design’, material.io, https://m3.material.io/components/top-app-bar/overview, January, 2023

Bottom App Bar

The users are used to the Floating Action Button at the edge of the Bottom App Bar. However, the new Material expands the bar vertically and keeps the button inside.

Source: ‘Material Design’, material.io, https://m3.material.io/components/bottom-app-bar/overview, January 2023

Navigation bars

The new navigation bar has a more distinguishable selected element by changing the icon to a fill version, bolding the label, and adding a shape around the icon in a different color.

Source: ‘Material Design’, material.io, https://m3.material.io/components/navigation-bar/overview, January 2023

Date picker

The main difference in the date picker is color theming and the component borders which are rounded and without a drop shadow.

Source: ‘Material Design’, material.io, https://m3.material.io/components/date-pickers/overview, January 2023

Time picker

Also, the time picker component is similar to the date picker component. I recommend a more detailed article about the implementation of the time picker component.

Check the article "MaterialTimePicker as an upgrade of the TimePickerDialog" (Patryk Kubiak, Feb 14, 2021).
Source: ‘Material Design’, material.io, https://m3.material.io/components/time-pickers/overview, January 2023

Design of other components

Other components which have the comparison between Material 2 and Material 3:

And here you can find a full list of the Material 3 components.

Conclusion

From its premiere in 2014, Material Design language went through dozen changes. After a while, there was an update to Material 2. That wasn’t a big deal. However, the major changes came with Material 3. The first Android system with Material 3 released in late 2021.

Today is the beginning of 2023, and I think the next 2–3 years are the time for validating and uploading improvements to Material 3.

Therefore, the upcoming versions of Android OS and different Google UI libraries for programmers will need some changes.

Let’s observe what Google will develop in the coming years!