Trippki is moving at full speed by rolling out its minimum viable product (MVP), or beta version, prior to its hugely anticipated token sale in early July.

“We are very excited to go beyond building our product through PowerPoint decks and conversations, but actually start the construction stage. The development team have done an incredible job, continually trialling and testing to ensure we create the best and user friendly platform. Our aim is to have the MVP ready by the end of June and everyone is behind this objective.” – says Mark Croston, Trippki’s Chief Commercial Officer.

While our development team are top class, so are our design team, and they’ve been working up different front-end styles and looks. We are calling on you, our community to help us shape Trippki, by telling us which design you like the most. More on this below.

But firstly, here’s detailed insights into the technology and the first functional developments.

Software development methodology and technology stack

Given that speed to market is critical we are using the Agile/Scrum software development methodology, with a carefully selected technology stack which includes:

  •  [backend] ASP.NET Core
  •  [database] PostgreSQL
  •  [deployment] Docker Compose
  •  [frontend] jQuery + Bootstrap
  •  [blockchain] Ethereum platform + ERC20 token
  •  [identity] – Civic
  •  [payment] – Coinbase, Stripe
  •  [wallet] – Metamask

Scrum at its’ core is based on iterative development through a series of Sprints. Each Sprint is made up of two-week periods with a clear view of what is being developed and then a review and approval process, which enables us to move forward in the right direction.

We have now completed Sprints 1 and 2 and as a result can highlight where we are to date and what still needs to be done.

A Trippki platform comes to life

During Sprint 1 we focused on one of the most critical areas – the guest flow. We have been able to look at search criteria, provide a list of hotels to choose from, allow users to select their preferred hotel, add the property to a basket, and complete with confirmation of booking.

You can see this user journey start to take shape in the steps, below:

Step 1 – Search for hotels based on certain criteria such as number of people and travel dates

Step 2 – Provide the use a list of hotels based on selected criteria

Step 3 – Present details of the selected hotel and its available rooms

Design 1,2 or 3, which look do you want for Trippki?

We have three designs, one of which will make it as the final front-end for the Trippki platform. We want to hear from you, so tell us your favourite style by emailing or via Telegram. Just tell us if its design 1,2, or 3 that catches your eye and sends you to travel heaven.

Get voting!

Design 1

Design 2

Design 3

What’s coming next?

Sprint 2 includes several enhancements picked up during Sprint 1, as well registration functionality for both the accommodation provider and the guest.

The accommodation provider will also be able to update details, including rooms, pricing and availability. This ensures both guests and properties are fully integrated into the Trippki ecosystem.

And, finally …

Alexander Karichensky, CTO added: “It’s a great experience to be working with the Trippki team. We are bringing a refreshing approach to the hospitality industry, aiming to benefit hotels as well as millions of travellers across the World.”

If you have any questions on the MVP, please feel free to contact Mark Croston at

Keep posted for more to come as we continue to evolve travel and rewards!

Connect with us on social:

Twitter: @Trippki_