TKEY: Topical News

The current situation has shown that the greatest amount of dependence on foreign companies can lead to stopping or slowing down the services that we are used to using.

Our team has decided to create a flexible solution that ensures independence and optimizes the processes that we will talk about today.

The situation in the world motivated us to reconsider approaches related to both financial flows and development in general. Foreign bank account lockouts, threats to disable SWIFT, GPay, Apple Pay, and, accordingly, indirect threats to remove applications from the App Store and Google Play tell us a lot.

Thus, dependence on one company, for example, Apple or Google, creates serious obstacles that need to be optimized at least, and it is better to exclude them altogether.

At the end of February, our team gathered to discuss these pressing issues and make the best decision, which was soon done. Foremost, we are interested in the availability of the service regardless of what is happening in the world, and even more so, regardless of what thoughts are “spinning” in the heads of large companies.

We should immediately note that the material consists of answers to questions and is also devoted to changes in a part of the platform code. Foremost, we will answer the questions, since the events inspired them by themselves; and then we will move on to the platform that we are currently developing.

Question — Answer

How is the situation in the company?

— The situation is normal; we quickly got our bearings in the situation and thereby saved the work of the services necessary to maintain the products.

Is there an impact of the situation on the company?

— At the moment, the influence is indirect, in particular, it affected the strategic jurisdictions in which the implementation was planned. On the other hand, new opportunities have appeared for our country, which can play a positive role for us.

Will the current situation affect the release?

— There is no direct influence; we are engaged in the technical part, we continue development. If we talk about the release delay, if it occurs, it will be insignificant; semi-annual and annual delays are completely excluded. The team is very serious.

Transition to the new system (requests)?

— In 2021, 99.7% of applications were processed; 100% of applications were verified. At the moment, there are applications that require corrections and applications related to illegitimate “blocks” in Core 1.0. Technical specialists are mostly now engaged in helping the team implement functionality, so the remaining 0.3% of applications will be processed later.

— We recommend entering an email address help-en@tkey.org to the mail’s “Contacts” list to quickly respond to support requests. You can check the official email addresses in the “Contact Centerhttps://tkey.org/en/contact-center.

TKEY Platform

The platform is being developed based on an ecosystem that includes best practices and connecting infrastructures: a tokenization system, a payment network, an exchange infrastructure, and a distributed registry.

Infrastructure is the basis, our backend, based on which the business logic of the future platform is implemented. Our stack is Rust, C/C++, Go, TypeScript.

Current events have motivated us to introduce more functionality than just the tokenized stock owners’ cabinet, which will allow us to get much more tools than we thought.

Abandoning adaptive layout and switching to the mobile version

We have decided to abandon the adaptive layout, which assumes a single structure of the platform pages that adapt to any device.

Let’s start with a reservation so that you can understand what we are talking about, since not all users know about the difference between the mobile version of the site and the adaptive layout.

In simple words, adaptive layout, when the entire design, interfaces are completely identical regardless of the device used, whether it’s a laptop or a smartphone. Thus, going to the site from a mobile or computer, you will have access to a single interface that adapts to the device.

The mobile version of the site is comparable to a mobile application when users receive full optimization for a mobile device. Thus, you will have access to an interface similar to a mobile application, and switch to the platform from a laptop, another interface adapted specifically for computers (desktops).

Our choice is the mobile version of the site and the web version of the site, which allows you to get functionality, interfaces, convenience, and speed of operation comparable to using a mobile application from a mobile device.

Thus, we do not oppose adaptability, but in our context, namely, in the context of exchange functionality, it is an ideal solution to have two versions; we will explain why.

The Property of Distribution

The mobile and web versions are two separate projects that do not depend on each other, which allows us to easily implement new “features” with a guarantee of availability. Thus, the mobile version and the web version are distributed and independent of each other.

I use adaptive layout, the team is forced to be within a single structure — this imposes restrictions; and in the case of two projects: mobile and web versions, we can implement “features” depending on the devices: our own for mobile, and others for desktop. The mobile version of the site uses the capabilities of a mobile device, and the web version uses the capabilities of a computer or laptop.

The simplest example is when the introduction of “features” with adaptive layout leads to incorrect display on a mobile device; if you look deeper, then a single adaptive structure pulls up a lot of unnecessary elements for a mobile device, which affects the speed of display and loading in general.

Customization

Using two projects, we easily create separate elements for the mobile and others for the web version; for example, a pop-up notification when hovering over the cursor in the web version, and in the mobile when clicking on an element.

Consider in our context: it is inconvenient and impractical to use unified exchange terminal interfaces for different types of devices; accordingly, it is much better to make convenient use of the exchange terminal, charts and other elements for a mobile device and separately for a computer, since this provides you with convenient management of all exchange functionality depending on the device.

In simple terms, if some “features” are convenient on the web version, and not convenient on mobile, then this becomes an obstacle to implementation, and using current practice, we implement “features” in such a way that they are convenient for each type of device; in general, a large platform opens up for creativity and more accelerated implementation of your functionality or design proposals.

Thus, the approach creates personalization for each of you, depending on the device you are using. If necessary, you can always switch from desktop to mobile and vice versa.

Independence from Google Play and App Store

Events have taught us that we need to choose flexible solutions, because removing an app from Google Play and App Store is equal to the lack of service, which in no way fits into our concept.

Thus, by releasing the mobile version of the platform, we exclude the influence of restrictions from Google Play and the App Store, since you can access the mobile version of the platform from your mobile and get access to functionality, and most importantly, to convenience comparable to a mobile application.

By the way, Pavel Durov spoke about such a concept at the time, when Apple began to declare the limitations of the Telegram application in the App Store; therefore, introducing such an approach, we had something to compare, something to rely on, something to think about.

Of course, the question may arise whether there will be a mobile application in the AppStore and Google Play — “Yes, there will be mobile applications, but using the mobile version of the platform is a guarantee of the availability of the service, regardless of political or any other events independent of the company, since the platform is accessible by URL.”

Availability Regardless of Device Power

It is important to note that the mobile version of the platform allows you to access regardless of the characteristics of your device, not everyone has the opportunity to buy the latest iPhone or Samsung, so the mobile version of the site is a guarantee of availability regardless of the characteristics of the device.

The mobile version facilitates and speeds up the loading of the platform as much as possible since unnecessary functionality is excluded from it, which usually overloads the pages.

The approach allows you to implement a responsibly familiar interface, closely similar to a mobile application, and provide functionality in a form that is acceptable for a mobile device and, accordingly, in a different form acceptable to desktop devices.

That is why we should use the web version and the mobile one; if part of the functionality is loaded lightning fast on a computer, then the same functionality is exhaustive for a mobile device, respectively, why overload our devices with you if you can make a customized approach.

Theses: Mobile and Web Version

  • Speed — pages are loaded much faster, which is important for the exchange service; the weight of the code is optimized for both desktop and mobile devices.
  • Usability — the design is personalized; in fact, the design is created separately for the mobile device and separately for the web version. With this approach, the arrangement of blocks, elements and other components are adapted to each type of device separately, one scheme for mobile devices, another for the web.
  • Saving traffic — the size of the downloaded code is much smaller, which allows you to display elements better and faster. In addition, if you use a VPN or Proxy, the packet delivery speed is also faster, since there is much fewer data than with the adaptive approach.
  • Switching — you can switch between versions: mobile and PC version (web version).

Theses: Platform

  • The team has found solutions to increase the availability of the service for both mobile and stationary devices; eliminate dependence on foreign stores App Store/Google Play.
  • The team is working on a regular release — development is going according to plan; delays, if any, are insignificant.
  • Annual, semi-annual, long delays are excluded.
  • The necessary tasks and arrangements for the release of the platform have been agreed.

In conclusion, we sincerely wish you peace of mind, an objective assessment of the situation, support for your loved ones and our Motherland!

Best regards,
TKEY Team

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
TKEY

TKEY

Official TKEY blog in Medium. Infrastructure for the financial ecosystem