In a transformative breakthrough poised to reshape the ride-hailing sector and the gig economy across Africa, inDrive ( www.inDrive.com) has made a bold advancement. The company has rapidly expanded its services to 20 African cities in less than 12 months throughout 2023, all while not charging any commission fees to its drivers.

Revolutionizing Ride-Hailing: inDrive Conquers 20 African Cities in 2023 with Groundbreaking Zero Commission Model

Rapido, the eight-year-old Indian bike taxi startup, is expanding into the cab market in the South Asian nation, where Uber and its homegrown competitor Ola dominate. The Bengaluru-based startup has begun a pilot of its cab service in the Southern city of Hyderabad,

India's bike taxi startup Rapido is getting into the cab business

An online ride-hailing mobility firm, inDrive has said it has been recording exponential growth in its operations in Nigeria, especially during the fuel subsidy removal that raised the pump prices of petrol from N195/litre to over N600/litre.

E-hailing firm records growth with subsidy removal

In December 2021, inDrive, former inDriver, soared to operating in more than 450 cities across 32 countries with 900 employees and an impressive record of 550 million completed trips.

inDrive @10 Reiterates Commitment to ExcellentP Delivery

MONTEVIDEO, Uruguay, October 26, 2023--inDrive, a global mobility and urban services platform, has added a new payment solution to its app in Brazil thanks to dLocal, a technology-first payments platform enabling global enterprises to connect with billions of consumers in emerging markets.

dLocal for Platforms brings cashless solution to inDrive Brazil

Drive, celebrated a remarkable achievement - its 10th anniversary. Oladimeji Timothy, the Business Development Representative for inDrive in

inDrive Celebrates A Decade Of Success

The newly launched, global non-profit film initiative Alternativa Film Project, founded by global technology company inDrive, announced the jury for the first edition of its Alternativa Film Awards, which will be held in December.

Cannes-winning director Brillante Mendoza to head jury at Indrive’s Alternativa Film Awards

Cannes-winning director Brillante Mendoza to head jury at Indrive’s Alternative Film Awards

As the campaign for India’s 2024 elections moves digital, social media influencers have emerged as a strong weapon for attempting to impact voter behavior. On May 26, Indian Prime Minister Narendra Modi’s Bharatiya Janata Party (BJP) celebrated his ninth year in power by hosting a gathering with 500 social media influencers at a cricket stadium

In the run-up to the 2024 elections, Indian politicians are courting influencers.

Get the most recent info and news about inDrive on HackerNoon, where 10k+ technologists publish stories for 4M+ monthly readers.

inDrive is a global IT and transportation platform  inDrive is one of the world’s fastest growing online ride-hailing services. Its services are available in over 700 cities in 47 countries throughout the world. The Company’s app has been downloaded over 150 million times. inDrive offers other services, including intercity transportation, freight and cargo services, as well as delivery services in different markets of operations.

inDrive is based in Mountain View, California, and operates regional hubs in the Americas, Asia, the Middle East, Africa and the countries of the CIS, and employs over 2,000 people. In early 2021, inDrive achieved unicorn status after closing a $140m investment round with Insight Partners, General Catalyst, and Bond Capital, which valued the company at $1.23 billion.


For more information visit www.inDrive.com


inDrive

Welcome to our brand new series - The HackerNoon Company of the Week, where we feature the top tech brands from our tech company database, making their evergreen mark on the internet. This unique HackerNoon database ranks S&P 500 companies and top startups of the year alike.This week, we present our business blogging partner__inDrive__ (former inDriver, short for “Independent Drivers“) - a ride-hailing service with one big edge from its competitors: the fare for the trip is set by the passengers themselves! Who doesn't like autonomy and self sovereignty ✊ Wanna be part of HackerNoon’s evergreen tech company database? Request Your Tech Company Page on HackerNoon! Meet inDrive: #FunFact Did you know that inDrive started as a small community of independent drivers in Yakutsk? According to the inDrive's ex-CTO: "As far as cab services were concerned, it was difficult and expensive to get a ride in Yakutsk before inDrive made its appearance on the scene. Things worked the old-fashioned way, and you had to call first and book a vehicle via the dispatcher and then wait a long time for the driver to arrive.In the winter of 2012, several smart guys created a Vkontakte group called Community of Independent Drivers of Yakutsk. In it, you could indicate that you needed to go from point A to point B and leave your phone number. Then a caring driver who just happened to be headed that way might call you to arrange a ride." From a small community of independent drivers to one of the top ride hailing services known globally, inDrive has come a long way! inDrive’s Featured Business Stories on HackerNoon inDrive.tech has shared some amazing content via the HackerNoon Business Blogging Program, and has generated 3 months 9 days 6 hours and 36 minutes of reading time! Here are our top 3 favorite stories by InDrive: Understanding Dynamic Programming So You Can Use It Effectively
How We Automated the Verification of Car Photos
How to Run 5000+ Tests on Mobile Devices Everyday; From inDrive's Playbook That's all this week, hackers!Stay Creative, Stay Iconic.The__HackerNoon Team__ Welcome to our brand new series - The HackerNoon Company of the Week, where we feature the top tech brands from our tech company database , making their evergreen mark on the internet. This unique HackerNoon database ranks S&P 500 companies and top startups of the year alike. This week, we present our business blogging partner__ inDrive __ (former inDriver, short for “Independent Drivers“) - a ride-hailing service with one big edge from its competitors: the fare for the trip is set by the passengers themselves! Who doesn't like autonomy and self sovereignty ✊ tech company database tech company database inDrive Wanna be part of HackerNoon’s evergreen tech company database? Request Your Tech Company Page on HackerNoon! Wanna be part of HackerNoon’s evergreen tech company database? Request Your Tech Company Page on HackerNoon ! Request Your Tech Company Page on HackerNoon Meet inDrive: #FunFact Did you know that inDrive started as a small community of independent drivers in Yakutsk? According to the inDrive's ex-CTO : inDrive's ex-CTO inDrive's ex-CTO "As far as cab services were concerned, it was difficult and expensive to get a ride in Yakutsk before inDrive made its appearance on the scene. Things worked the old-fashioned way, and you had to call first and book a vehicle via the dispatcher and then wait a long time for the driver to arrive.In the winter of 2012, several smart guys created a Vkontakte group called Community of Independent Drivers of Yakutsk. In it, you could indicate that you needed to go from point A to point B and leave your phone number. Then a caring driver who just happened to be headed that way might call you to arrange a ride." "As far as cab services were concerned, it was difficult and expensive to get a ride in Yakutsk before inDrive made its appearance on the scene. Things worked the old-fashioned way, and you had to call first and book a vehicle via the dispatcher and then wait a long time for the driver to arrive.In the winter of 2012, several smart guys created a Vkontakte group called Community of Independent Drivers of Yakutsk. In it, you could indicate that you needed to go from point A to point B and leave your phone number. Then a caring driver who just happened to be headed that way might call you to arrange a ride." "As far as cab services were concerned, it was difficult and expensive to get a ride in Yakutsk before inDrive made its appearance on the scene. Things worked the old-fashioned way, and you had to call first and book a vehicle via the dispatcher and then wait a long time for the driver to arrive. In the winter of 2012, several smart guys created a Vkontakte group called Community of Independent Drivers of Yakutsk. In it, you could indicate that you needed to go from point A to point B and leave your phone number. Then a caring driver who just happened to be headed that way might call you to arrange a ride." From a small community of independent drivers to one of the top ride hailing services known globally, inDrive has come a long way! inDrive’s Featured Business Stories on HackerNoon inDrive.tech has shared some amazing content via the HackerNoon Business Blogging Program , and has generated 3 months 9 days 6 hours and 36 minutes of reading time! Here are our top 3 favorite stories by InDrive: inDrive.tech HackerNoon Business Blogging Program Understanding Dynamic Programming So You Can Use It Effectively How We Automated the Verification of Car Photos How to Run 5000+ Tests on Mobile Devices Everyday; From inDrive's Playbook Understanding Dynamic Programming So You Can Use It Effectively Understanding Dynamic Programming So You Can Use It Effectively How We Automated the Verification of Car Photos How We Automated the Verification of Car Photos How to Run 5000+ Tests on Mobile Devices Everyday; From inDrive's Playbook How to Run 5000+ Tests on Mobile Devices Everyday; From inDrive's Playbook That's all this week, hackers! Stay Creative, Stay Iconic. The__ HackerNoon Team __ HackerNoon Team

Meet inDrive: The HackerNoon Company of the Week

মিট ইনড্রাইভ: সপ্তাহের হ্যাকারনুন কোম্পানি

Lernen Sie inDrive kennen: Das HackerNoon-Unternehmen der Woche

Conozca inDrive: la empresa de la semana de HackerNoon

Rencontrez inDrive : l'entreprise HackerNoon de la semaine

इनड्राइव से मिलिए: इस सप्ताह की हैकरनून कंपनी

inDrive のご紹介: 今週の HackerNoon 企業

inDrive에서 만나보세요: 금주의 HackerNoon 회사

Conheça inDrive: a empresa HackerNoon da semana

Встречайте inDrive: компания недели HackerNoon

inDrive'da Tanışın: Haftanın HackerNoon Şirketi

Gặp gỡ inDrive: Công ty HackerNoon của tuần

结识 inDrive：本周 HackerNoon 公司

Hi everyone! My name is Michil Androsov and this is the second article in my series on the history of , where I offer an inside look at the creation of our unicorn company from the perspective of a simple developer. The first article is available . In it, I talked about how I joined the company, how we expanded the development team, and how we went international. inDrive here This article will cover the middle period of my career at inDrive—from about 2016 to 2020. At the time, the company was beginning to stand on its own two feet and rapidly develop in all kinds of new directions, which I'll discuss in more detail below. The Business After our first successful launches outside of Yakutsk, we were finally starting to recognize the power of our business idea. We began to wonder, "What if we really manage to take over the planet?" After all, living far up north, , you always feel quite separate from the rest of the world. It seems like everything's happening so far away, which actually gives us a pretty unique perspective. And at the time, all of our work with inDrive felt almost like a game to me. deep in Siberia Over this period, the company began to launch extensively. When we'd start operations in a new country, we might launch dozens of cities within a single month. We expanded beyond Russia and launched in Kazakhstan, where—despite a variety of obstacles—we quickly became the country's №1 ride-hailing service. To this day, Kazakhstan remains one of our top markets. When launching in a new city, we adopted a strategy of " ". As our CEO would say, if a city was ready for our service, it should be able to ignite from the smallest of sparks. So, if the grass in one city wasn't dry enough, we wouldn't try to soak it in gasoline. Instead, we'd just move on to the next one. This helped us expand quickly without spending too much money. burning dry grass In fact, a number of cities simply launched on their own. People would hear about this great new service, called inDrive, in a neighboring city. They'd download the app for themselves, and the city would launch without us. There were even a few self-launched cities that took off without any investment on our part. Of course, not all launches were a success. I remember our first back in 2018. We made all the preparations, recruited drivers, and advertised our service. At first, everything seemed to be working out, and our numbers were growing day by day. USA launch We were pleasantly surprised. Was it really that easy to launch in one of the world's largest markets? After all, if you can make it in the US, you can make it anywhere—at least, that's what I thought. But our joy quickly became disappointment: We were faced with a huge industry of fraudsters cashing out stolen credit cards and using them on our service. So, we decided to scrap our American plans and wait for better days—which finally came in 2023. We launched for the second time in the USA, with much better results. This launch is still ongoing. We are currently operating in Miami, and will soon expand to new cities. Looking back, we were being simple and naive. However, we continued to learn from our mistakes and push forward. The Product and Technology We've always believed that our service should be simple and fail-proof, like a . Of course, this has led to accusations that the app isn't "pretty" enough, despite being packed with features. Nokia 3310 In many countries, we had to adapt to local legislation and user needs. That’s why the inDrive app in Almaty might look completely different from the one in New York. Nevertheless, we have been working on making the app "prettier" in all countries over the past years, and I personally think it looks quite modern now. Outside of Russia, inDrive gained a range of new modules, starting with intercity rides and freight delivery, which are now available in countries across the globe. In certain markets, such as Kazakhstan, they are even more popular than our taxi vertical. During this time, our approach to product planning was simple: At the end of every quarter, our CEO would arrive back from his trips to our launch cities, open his laptop, and explain our goals for the upcoming period. Usually, these came from driver and passenger requests. We could have tasks of all different sizes, from introducing card payments to changing the color of the order button. Our CEO played (and continues to play) a crucial role in the development of the company. While he is both an excellent motivator and strategist, he’s also a skilled manager who understands how the product works. Even now, he personally flies to new launch countries, studies the market, conducts customer development, interacts extensively with users, and gathers feedback on the service. On the development side, we quickly realized that our existing code would not be able to support our rapid business growth. Soon, the app would start to lag and decline in quality. So, we decided to rewrite the more "complex" parts of the code. In addition to the PHP monolith, we eventually got ourselves a— —Golang monolith. The entirety of our infrastructure lay on the shoulders of two guys who knew all the inner workings of our enormous machine. If the service ever crashed, they were prepared to turn on their laptops and fix it at any time, day or night. ba-dum-tss We also got our first QA specialist for full-scale testing. This made our lives incredibly easier. Before our QA, we had been spending a lot of time and effort testing new functionality and updates by ourselves, and checking how they interacted with existing versions. Little by little, mobile developers began to join our team, albeit with some difficulty. After all, you needed Apple products to get into iOS development, and those could be difficult to find in Yakutsk. This meant that we struggled to recruit local iOS developers, and our iOS team would sometimes lag behind our Android team when it came to releasing new features. I remember one time in Kazakhstan, when our app was blocked at the government level. I won't get into the details, but to reverse the block, we had to introduce a number of different features, including user instructions, automatic address changes, proxies, and more. In the end, we restored our capabilities in the country and officially reversed the block after a few years. I remember writing to the CTO of a large CIS news site that had also been blocked in Kazakhstan, and asking how he had managed to keep business going. Many of our features were developed through a series of trials and errors—or stumbled upon by chance—although they might seem completely obvious in hindsight. Take our call-free ride-hailing system, for example. If you haven't read the , I'll quickly summarize it here. first article Previously, when an inDrive passenger would create their order, a driver would see their request in the orders feed and call them right away. And this wouldn't be just one driver either; these orders were being sent to anyone nearby. Of course, this led to situations where multiple drivers would see an order and try to call the passenger at once. Typically, the first person to contact the passenger would get the order. Here's where the problem came in: Drivers would click on a ride without reading the order details, and then all try to call the passenger at the same time. So, we created something called a "buffer." When drivers press the order button, there's a short delay, which gives us time to collect all potential offers. This way, drivers don't have to rush, and they have time to read the order details in full. Then, based on the drivers' ratings, the system selects which of them will be able to call the passenger first. This was a significant improvement to our old version. Although the call-free system is now used by practically every ride-hailing app, we actually came up with ours by chance. In 2016, we launched in Yekaterinburg and introduced the "Guardians," who were specially selected drivers that could accept orders that typical drivers couldn't. We would send them special push notifications about exclusive orders. However, we soon realized that these push notifications weren't working very well because they were easy to miss. And that's when we remembered one of our existing features, called "personal orders," which allowed the passenger to simply select the closest driver on the map and send the order straight to them. We decided to use this feature when sending orders to our "Guardians." It took off immediately and worked so well that we then decided to expand it to all drivers. Of course, the personal orders feature might seem obvious now, but we discovered it through a series of trials and errors. The Team Up until 2019, our team was fully made up of Yakutsk locals. At the time, we wanted to help our homeland grow — and the local people along with it. inDrive had always held a strong mission and values. These values resonated with each employee, and we strived to uphold them. This was a period of powerful drive and energy. Every day, I would wake up in a good mood, knowing that my friends and good coffee were waiting for me in the office. That and plenty of interesting work, of course. inDrive was known for being a social company. Our team was young and carefree, which meant we worked hard and played hard. Every year, we'd take a company trip abroad, whether to Egypt, Thailand, Kazakhstan, or somewhere else entirely. Imagine an entire plane of colleagues escaping the –50-degree Celsius weather in Yakutsk to visit sunny +35-degree Thailand! It was great at the time, but unfortunately, these big company trips aren't possible anymore with a workforce of several thousand employees. By 2019, we hit a hiring roadblock. Business was booming, and any professionals in Yakutsk capable of handling the tasks and workload were already working for us. So, we decided to open a development office in Moscow. As the head of the iOS team, I was charged with opening the Moscow branch. We had a lot of flexibility during this time, and employees were free to contribute to the company in any way they saw fit, as long as it benefited the business. I entered a new phase in my life. I moved to Moscow and started the process of opening the new office, from choosing a business center to installing special lights with the company logo. Now that a few years have passed, I can look back at that time fondly. But back then, I would often think: "Why did I do this to myself? Why'd I take on all this renovation work?" Our main problems had to do with the company in charge of the renovation. At one point, they were so behind schedule that I even had to help them install the electrical wiring in the workspaces. I remember one specific evening, when we stayed late to assemble furniture. I could see that my colleagues were tired and depressed, so to lighten the mood, I asked " " At the time (and to this day), Belorusskaya was one of the most expensive areas in Moscow, like Times Square in New York. It was also home to a number of impressive IT offices. Of course, we just laughed and got back to work. Why the long faces? Cheer up! Next year, we're opening an office on Belorusskaya! By the end of 2019, we had our first developers at the Moscow office. Sometimes, it would seem like they were from another planet. During their interviews, they'd say things like, "We work in sprints. I finished all my tasks, then came here" (and it'd only be Thursday afternoon). Or they'd say, "We work three days from home and two days from the office." That was something completely new for me. inDrive was entirely office-based at the time, and everyone was expected to contribute fully. We weren't working with any kind of Kanbans, scrums, story points, or sprints. Conclusion We entered 2020 with a lot of optimism. Our new development office in Moscow had opened, and we were working with a great team. I was living in the capital, business was growing, and investments were on their way! When the company received investments, we would conduct a cashout, meaning employees could sell a small portion of their stock options for real money. Everything seemed to be going our way, like we were living in a movie. Unfortunately, though, this is the point in my story where things get a little darker, like in the Harry Potter movies. Suddenly, we were faced with a huge challenge. In 2020, the world was shut down by the coronavirus. inDrive closed their offices and we started to work from home—something we had always been firmly against. Life took on new rules and we had to quickly find our footing. We developed new processes, took our first online calls, and sent laptops home to new employees. Then, in mid-2020, I became the CTO of inDrive. It was a surprise even for myself. I was placed in charge of 50+ developers, 4 distributed teams, and the two offices in Moscow and Yakutsk. Of course, there were plenty of challenges, which I'll discuss in more detail in my next article. My joke about our office on Belorusskaya quickly became reality. At the end of 2020, we opened an office in one of the best business centers in Moscow, right on Belorusskaya Square, alongside other cool IT companies. P.S.

Building a Unicorn: The inDrive Tech Journey from Local Startup to Global Phenomenon 

ইউনিকর্ন তৈরি করা: স্থানীয় স্টার্টআপ থেকে গ্লোবাল ফেনোমেনন পর্যন্ত ইনড্রাইভ টেক জার্নি

Aufbau eines Einhorns: Die inDrive-Tech-Reise vom lokalen Startup zum globalen Phänomen

Construyendo un unicornio: el viaje tecnológico de inDrive desde una startup local hasta un fenómeno global

Construire une licorne : le parcours technologique d'inDrive, de la startup locale au phénomène mondial

यूनिकॉर्न का निर्माण: स्थानीय स्टार्टअप से वैश्विक घटना तक इनड्राइव टेक यात्रा

ユニコーンの構築: 地元のスタートアップから世界的現象への inDrive テクノロジーの旅

유니콘 만들기: 로컬 스타트업에서 글로벌 현상까지의 inDrive 기술 여정

Construindo um unicórnio: a jornada tecnológica do inDrive, de uma startup local a um fenômeno global

Создание единорога: технологическое путешествие inDrive от локального стартапа к глобальному феномену

Bir Tekboynuz Yaratmak: Yerel Startup'tan Küresel Fenomen'e inDrive Teknoloji Yolculuğu

Xây dựng kỳ lân: Hành trình công nghệ inDrive từ khởi nghiệp địa phương đến hiện tượng toàn cầu

打造独角兽：从本地初创企业到全球现象的 inDrive 技术之旅

Despite the somewhat pretentious title, the purpose of this article is not to present a success story or give some “hot tips” based on useless platitudes and truisms. I just want to share a few stories about the company I've spent almost my entire professional career with. About how this service came to life in a distant and cold city called Yakutsk, I share my perspective on inDrive from an engineer's point of view. Hi everyone! My name is Michil Androsov, and I've been with for 10 years now. I joined the company when there were three people on the development team, and left it as CTO with 500 people under my command. Over the years, the company has grown from a local startup to a unicorn company with hundreds of invested by the world's top funds. inDrive millions of dollars (former inDriver, short for “ dependent s“), is a ride-hailing service from (the capital of ) with one big difference from all the others: the fare for the trip is set by the passengers themselves. inDrive In Driver Yakutsk Sakha Republic Unlike its competitors, inDrive’s pricing model involves no complicated algorithms based on hundreds of criteria. The entire system is as transparent as it can be, with only two parties involved in the process: the driver and the passenger who negotiate the fares amongst themselves and agree on a price that works for both parties. This is a self-balancing system. Sakha Republic, also known as Yakutia, is a republic located in the Far East of the Russian Federation. Mostly inhabited by the local indigenous people, the Yakuts, but quite multiculturalized. The republic has a reputation for an extreme and severe climate. The Yakutsk vibe Here is why the service emerged in Yakutsk, of all places. In my book, two reasons explain this: With temperatures outside dipping down to 50 degrees Celsius below zero, rather than go for a walk in the park or take a nature hike, people tend to stay at home. They have to find ways to keep themselves entertained and, more often than not, they spend their time in front of a computer. Combined with the top schools that lay a special focus on physics and math, of which there are many in the area, there is a chance that a lot of these kids will become programmers. At least, that's how I explain this to myself. Cold climate. Because of this, the Internet was very expensive and slow. The Internet worked with radio relay technology. And you had to pay for every megabyte. A couple of downloaded movies from the internet could cost a worker's salary. So employees of Internet service providers would download something from the Big Internet and put it on the . I remember some of the guys who even engaged in satellite fishing. Isolation from the mainland. intranet It’s due to these two factors that Yakutsk ended up having its own"Internet", and with it the Internet portal (currently down) - local web portals like yahoo or dmoz, craigslist, napster, image photo board, news, forums all in one. It was a local variety of Alphabet, and all of the few IT specialists in Yakutsk wanted to get a job there. The company that owned the portal was called Sinet(short for Sakha Internet) — a company within which inDrive was soon established. Ykt.ru It's worth pointing out here that in addition to Sinet, there was a large game-development company called in Yakutsk, and it also acted as a magnet for local IT guys. That company started with two brothers from the small northern village of Khonuu who borrowed some money from their parents to start developing their first indie game. As things stand today, inDrive and Mytona have "moved" out of Russia. Mytona Independent Drivers As far as cab services were concerned, it was difficult and expensive to get a ride in Yakutsk before inDrive made its appearance on the scene. Things worked the old-fashioned way, and you had to call first and book a vehicle via the dispatcher and then wait a long time for the driver to arrive. To make matters worse, your call might be forgotten and then the wait for the car exceeded all possible limits. A separate pain point was the New Year holidays(major holiday in the country, two weeks of partying, no one works), when cab services upped their prices multiple times over, thus pushing the passengers over the edge. In the winter of 2012, several smart guys created a group called "Community of Independent Drivers of Yakutsk". In it, you could indicate that you needed to go from point A to point B and leave your phone number. Then a caring driver who just happened to be headed that way might call you to arrange a ride. At the end of the trip, the passenger had to leave money with the driver to cover the cost of gas. Vkontakte Sure thing, very soon, instead of gas price compensation, people started paying for the ride. Over a short time, the group gained massive popularity and began to gradually cut out traditional cab services. inDrive. Early days At that time, Arsen Tomsky, the director of Sinet, saw this group as a promising idea for expanding his business and decided to buy it out. Essentially, that point marks the beginning of inDrive's existence. In October 2013, I joined the company as the third developer when the startup was in its fifth month of operations. At that time, the app's Android version was already available, and our guys were looking for an iOS developer. Before joining the company, I worked for a year in a small startup studio developing interactive books on iPad for kids, first in our native language. Right at that point, I was thinking of changing jobs. I had one big advantage going for me - my MacBook, which was a rarity in Yakutsk at the time. I thought this was my chance to try and get a job at Sinet. I had no experience in iOS development, but somehow (most likely due to a lack of suitable candidates) I succeeded in landing a job at my dream company. iOS development was native: I coded in Objective-C. Now the situation hasn't changed much, the only difference being that is now commonly used instead of Objective-C. While Android was coded in Java, the backend was written in PHP. Many of the things laid down back then remain at the core of the inDrive codebase today. Swift The core iOS development team at that time was just me. In 2015, a second person came on board to join me. Once a third one was hired in 2016, we started growing very fast. There were no cross-platform teams back then— just iOS-, Android-, backend development teams, and QA testers. It makes me wonder how the inDrive driver accepted ride requests in those days. It was called a : a passenger places an order, nearby drivers simultaneously see it on their request list, and those who like the offer click on it. The peculiar thing back then was that we just connected a driver and a passenger via the cellular communication network! Sometimes, multiple drivers would call in for the same ride request at the same time. After the call, we would show the passenger a list of all the drivers who had called so they could pick the most suitable one. The whole set-up seemed to operate based on the principle of "the order goes to whoever calls first". Because of this, there were customer support complaints from drivers reporting that they didn’t have enough time to pick up the order. call-based arrangement For a long time, there was a legend that iOS had a much higher chance of securing an order than Android. There was some truth to this, as the interface did indeed run faster on iOS. For a long time, we did not introduce"call-less" order acceptance processes, which were more commonly used by other ride-hailing services, thinking that passengers would have more trust in the driver if they had time to talk to each other on the phone before the ride. Obviously, such a strategy had its limitations, and quite serious ones at that. Also, the first version of the app had an interesting tab called "Available Drivers". By clicking on it, you could go to the map, find an available driver, call them personally, and arrange a ride. Understandably, back then there were no encrypted connections yet. In addition, there was a third way to find a driver: after creating a ride request (order), I could find a suitable driver on the map and send them my offer via a personal message. This was called "Personalized Order”. Nowadays, the guys sometimes miss the days when everything was as easy, fast, and as fun as possible. I didn't know what repositories were, and after the release of each version, I archived the project folder and saved it on my hard drive (hundreds of archives are still stored there) and Google Drive. In the early years, our project in Xcode was called , whereas our product tasks were written down directly on the whiteboard. startPage I wasn’t yet familiar with the basic programming patterns and architectures of iOS development. The end result was a stack of Massive View Controllers and storyboards with dozens of screens. This was genuine StackOverflow programming. Expanding beyond Yakutsk Gradually, our startup team began to grow. New people joined, and the first simple processes emerged. In 2014, the company already had 10 staff members. It was at that time that we flew over to Novosibirsk to participate in a conference. It was the three of us, the whole development team. This was another significant milestone in the company's history, as in Sakha Republic you feel isolated from the big wide world outside. Trips like this were a major event for us. At the end of 2013, we were joined by Sasha Pavlov, the creator of the VKontakte group, which was bought out by Arsen Tomsky. With him on board, we began our first attempts to launch in other cities. One day, Sasha flew to Sakhalin to talk things over with drivers. He printed out some promotional pamphlets and started handing them out in the mall parking lot, but was chased away by security. Eventually, though, we had a successful launch in Sakhalin and it immediately showed excellent growth. Then we started launching in other northern and eastern Russian cities: Irkutsk, Tomsk, etc. These areas resemble Yakutsk in that they have similar severe climatic conditions, and there are no other major apps there. In those cities, the app started showing growth almost instantly. We used to sit in our little office and daydream, "Just imagine, one day we will be earning more than ." We had a laugh, but in reality that moment came very quickly. Ykt.ru Our CEO always wanted a bigger story, and not related to Yakutsk. He's an entrepreneur to the core, and he always seeks new challenges. It seemed obvious and logical to us, so no one questioned why we were doing what we were doing. It was always cool to figure out how much we, some guys from Yakutsk, could compete with the big companies. At that time, our main competitors were and . We weren’t thinking about yet. But soon we had to give the situation plenty of thought, but I'll tell you more about it in my next posts if you're interested. Taxi Maxim Yandex Taxi Uber This is my first experience writing an article and I want to write more about the history of inDrive’s evolution, how I became CTO, and what technical and non-technical challenges we faced and had to overcome. So it would be awesome to get your feedback on what could be improved upon here and what you'd be interested in reading about in future posts. P.S. Share them in the comments! P.P.S. The milestones of Sinet’s and inDrive’s evolution are described in more detail in the book by the company's CEO: “inDriver: From Yakutsk to Silicon Valley”.

Building a Unicorn: My Decade-Long Career With inDrive

একটি ইউনিকর্ন তৈরি করা: ইনড্রাইভের সাথে আমার দশক-দীর্ঘ ক্যারিয়ার

Ein Einhorn bauen: Meine jahrzehntelange Karriere bei inDrive

Construyendo un unicornio: mi carrera de una década con inDrive

Construire une licorne : ma carrière d'une décennie avec inDrive

एक यूनिकॉर्न का निर्माण: इनड्राइव के साथ मेरा एक दशक लंबा करियर

ユニコーンの構築: inDrive での私の 10 年にわたるキャリア

유니콘 만들기: inDrive를 사용한 나의 10년 경력

Construindo um unicórnio: minha carreira de uma década com inDrive

Создание единорога: моя десятилетняя карьера в inDrive

Bir Tekboynuz Yaratmak: inDrive'daki On Yıllık Kariyerim

Xây dựng Kỳ lân: Sự nghiệp kéo dài hàng thập kỷ của tôi với inDrive

打造独角兽：我与 inDrive 长达十年的职业生涯

HackerNoon editorial team has launched to celebrate their achievements and share their struggles. We need more women in technology, and by sharing stories, we can encourage many girls to follow their dreams. ! this interview series with women in tech Share your story today Tell us about yourself! Thank you for having me! As a leading Product Manager at InDrive, a global ride-hailing service, I’m passionate about making transportation more accessible and efficient. With experience in the tech industry, surpassing more than five years, I’ve spearheaded product launches across 17 countries, impacting the lives of millions of users. Recently, I was honored to serve as a jury member for a 2023 Globee Women in Business Awards and the AI for Humanity Hackathon organized by Burning Heroes. As of 2024, I lead a talented team developing international ride-hailing services at InDrive, collaborating with colleagues from over 15 countries to ensure a seamless experience for riders and drivers worldwide. In particular, I specialize in optimizing driver-sender matches, creating solutions for users to make better deals within our platform, and using the latest cutting-edge technology, such as machine learning and economic principles. Such an approach enhances customer experience and platform efficiency – a win-win for everyone. Why did you choose this field in the first place? I’ve always been fascinated by technology’s potential to solve real-world problems and, most importantly, improve people’s lives. Plus, the fast-paced nature of tech keeps things exciting for me, with new challenges and opportunities to learn emerging technologies. In other words, the field offers a constant learning curve. Besides that, I'm particularly drawn to the collaborative culture where knowledge is shared openly within the tech community. This allows me to create solutions practically for every industry — medicine, AI, real estate — that can impact millions of people worldwide, which truly motivates me. What tech are you most excited/passionate about right now and why? While large language models (LLM) are the most anticipated development, several other technological advancements capture my interest. Here are a few areas I find particularly promising: New technologies, such as advanced biosensors and generic testing, tremendous possibilities for detecting severe diseases like cancer and autoimmune disorders at earlier stages. Additionally, the growing role of big data and its practical interpretation from medical scans (MRI and CT) can lead to better diagnoses, personalized treatment plans, and improved preventative care. In fact, several innovative startups are working in this direction, and I'm eager to see their progress. Healthcare advancements: offer Fully automating back-office processes through AI would benefit tech companies, manufacturers, and other industries. While it may seem ordinary, solving this narrow problem could have a massive impact on industry and enterprises’ efficiency and productivity. AI-powered enterprise automation: Platforms allowing users to create websites without coding are changing how people access technology creation. Recently, an AI tool code and communicated as a software engineer! Just imagine building mobile apps, data dashboards, or even simple workflow tools—all without writing a single line of code. These no-code tools and numerous pilot engineering tools are slowly transforming the landscape, empowering people, and reducing production costs in the digital world. Development through no-code tools: wrote Beyond my interest in the field, the increasing complexity of transportation technologies gives me goosebumps—from self-driving cars and trucks to AI optimization and next-generation predictive analytics. Future of transportation: What tech are you most worried about right now and why? One primary concern about generative AI is the potential misuse of personal data to train these models. Although data privacy regulations are strengthening globally, there’s a lingering suspicion that corporations can still misuse personal data to gain an unfair advantage in the market. This raises a crucial question: Are these regulations compelling, and can the non-tech person understand them? What are your hobbies and interests outside of tech? I enjoy various activities that challenge me mentally and physically in my spare time. Take, for instance, tennis. It is a great way to hone my focus and develop a winning mindset. Its practice also taught me the importance of teamwork and effective conflict resolution. At the same time, psychology is another area I’m passionate about. Currently, I’m delving into Jungian Analysis, which helps me communicate with platform users unbiasedly and glean deeper insights from our conversations. This knowledge and my understanding of cultural differences foster greater empathy — a crucial skill when working on a product used in over twenty countries. I find it helpful to take conversation pauses, ask thoughtful questions, and practice active listening to bridge cultural gaps. Let's talk about breaking the glass ceiling. What were the biggest challenges you faced as a woman in tech, and how did you deal with them? Undoubtedly, the glass ceiling in tech remains a persistent issue, and statistics paint a clear picture – men significantly outnumber women. For instance, women for 25.3% of Google’s new tech hiring in 2023, compared to 20.8% in 2018. At the same time, Microsoft’s workforce to 33.1% in 2023, up from 29.2% in 2018. Other companies, such as Facebook and Apple, showed similar trends. The numbers reveal a stark reality: only one in three women work in the , compared to management, consulting, legal, or finance. accounted rose tech sector Several factors contribute to this disparity. For example, societal expectations can differ for men and women, with women often taking on greater childcare and household responsibilities. Additionally, tech can feel like a male-dominated environment, lacking role models for female leadership and fostering unconscious bias against women leading times in a traditionally masculine style. To navigate these challenges, I choose teams with inclusive cultures and actively support other women in tech. Practically speaking, I am an active participant in communities like Women in Tech that offer invaluable support networks where we can share experiences, empower each other, and curb any misogyny. Though a topic of debate, positive discrimination holds potential in the current landscape. When equally qualified candidates exist, a diverse slate can highlight potential unconscious bias within homogenous environments. The most significant challenge is ascending the corporate ladder within a male-dominated hierarchy. While some advise leveraging charisma to stand out, a more sustainable approach lies in achieving goals through shared objectives and mutual respect. Focusing solely on gender differences can reinforce bias. In contrast, a business-oriented approach fosters collaboration and paves the way for advancement. Any questionable misogynistic story/situation you faced/handled and you want to share with the HackerNoon Fam? While I may not have personally faced misogyny, it's essential to acknowledge that these situations still exist. We've all likely witnessed or heard about them. That's why standing with those who challenge inequality and fight for a more inclusive space is crucial. What's your biggest achievement that you're really proud of? One of my most significant achievements was leading the launch of intercity delivery product, which is now the leader of the mobility market in its country. It resulted in 47.4 million monthly active users by 2023. I managed five teams with numerous stakeholders and oversaw all aspects of the project, from product research to market assessment to financial planning. The product went live in over 100 cities nationwide within several months. In your opinion, why do we see this huge gender gap in the tech industry, and how can we reduce it? As mentioned earlier, the significant gender gap in tech stems from societal expectations and the industry's current culture. To bridge this gap, we need a two-pronged approach. First, we need to cultivate a more inclusive culture within tech. Initiatives like mentorship programs and fostering diverse hiring practices can help. Second, we need to address societal expectations. Normalizing women in tech and providing them with the support they need to balance work and life can create a more equitable future for the industry. Who is your tech idol? Why? Tech is full of inspiring figures, and a few people who stand out for me are Julie Zhuo, Lenny Rachitski, and Paul Graham. Julie's journey from intern to VP of design at Facebook, especially as a minority woman, is a powerful testament to her talent and perseverance. Her recent article on navigating company politics completely changed my perspective on workplace conflicts and empowered me to be more constructive. Sharing valuable insights while in leadership demonstrates her commitment to giving back and helping countless professionals. Lenny Rachitski's insightful product management blog and interviews with industry leaders offer a goldmine of knowledge for anyone in the field. His ability to spark discussions relevant to global communities makes his work exceptionally valuable. I deeply appreciate his contributions - these insights from experienced professionals are invaluable in the market. Finally, Paul Graham's writing on is a constant source of motivation. I often revisit it for inspiration. great work Do you have any advice for aspiring girls who want to join the field? Make sure your passion for this field is the driving force behind your decision. It can be challenging without support, so I recommend building a strong community around you. Look for mentors, participate in online forums, or attend industry events to connect with others. Get real-world experience through volunteering or internships related to your field. The stronger your network and the more you learn, the more opportunities will come. However, it's essential to find something you enjoy. Remember, your career path is yours to define. Don't be afraid to explore and change course if needed. And, finally, believe in yourself – no one can tell you what's impossible.

Normalizing Women In Tech: Interview With Ksenia Mayorova, Leading Product Manager At InDrive

of this article, we described how to quickly and easily build an infrastructure for running UI tests on Android using Appium and Selenoid. We are continuing our story to explain how we incorporated the launch of UI tests in iOS into the process. In the first part Scaling with GGR The maximum number of parallel workflows within a host is limited by its resources. Thus, we needed a tool for combining multiple hosts into one cluster. For this, we use the (GGR) from the folks at Aerokube. Based on the description in the documentation, GGR is a load balancer used for creating scalable and highly available Selenium clusters. Go Grid Router The project with the tests runs a query in GGR as part of the process used. It polls the Selenoid parameters specified in its configuration and distributes the load among them based on the platform used, the availability of free flows, and the predefined specific weight of each Selenoid. Deploying GGR and GGR UI is easy: Install . Docker Create a directory for GGR configuration files . mkdir -p /etc/grid-router/quota Create a file . users.htpasswd $ htpasswd -bc /etc/grid-router/users.htpasswd test test-password Create a quotas file where you specify the address of the deployed Selenoid as the host: $ cat /etc/grid-router/quota/test.xml
<qa:browsers xmlns:qa="urn:config.gridrouter.qatools.ru">
<browser name="android" defaultVersion="10.0" defaultPlatform="android">
  <version number="10.0">
    <region name="1">
      <host name="0.0.0.0" port="4444" count="1"/>
    </region>
  </version>
</browser>
</qa:browsers> Run the GGR container: docker run -d \
  --name ggr \
  -v /etc/grid-router/:/etc/grid-router:ro \
  --net host aerokube/ggr:latest-release \
  -listen=:4445 -guests-allowed In the tests project, change the Appium port to the port of the running GGR: val driver = AndroidDriver(URL("http://localhost:4445/wd/hub"), capabilities) Run the GGR UI container: docker run -d \
  --name ggr_ui \
  -p 8888:8888 \
  -v /etc/grid-router/quota:/etc/grid-router/quota:ro \
  aerokube/ggr-ui:latest-release Run the Selenoid UI container where we pass the GGR UI port via : selenoid-uri docker run -d \
  --name selenoid-ui \
  -p 4446:4446 \
  --link selenoid:selenoid \
  aerokube/selenoid-ui:1.10.4 \
  --selenoid-uri "<http://ggr-ui:8888>" Our Selenoid UI should now display the status of all Selenoid clusters connected to GGR. Now, we proceed to the running of tests on iOS We use our own Mac mini farm to run UI tests on iOS. The farm can similarly be assembled from decommissioned but operational MacBooks. Alternatively, they can be . The following needs to be installed on each host: rented Appium (Appium 2.x must be used when one is working with iOS≥16). Xcode. Some early problems We were unable to replicate the structure used in running Android tests because we couldn’t find a way to run iOS simulators in Docker containers. One option that we considered was running , but we ran into doubts about the legality of its use for any purposes unrelated to . So, we decided to go a different route. Docker-OSX OS X Security Research Iteration #1: GGR→Appium We added Appium (port 4723) as a Selenoid host for iOS tests in the previously created GGR config file: <qa:browsers xmlns:qa="urn:config.gridrouter.qatools.ru">
<browser name="android" defaultVersion="10.0" defaultPlatform="android">
  <version number="10.0">
    <region name="1">
      <host name="0.0.0.0" port="4444" count="1"/>
    </region>
  </version>
</browser>
<browser name="iPhone 14" defaultVersion="16.2" defaultPlatform="iOS">
  <version number="16.2">
    <region name="1">
      <host name="0.0.0.0" port="4723" count="1"/>
    </region>
  </version>
</browser>
</qa:browsers> In such a case, the iOS scheme looks like this: The structure used in this iteration is operational. The problem is that, in this case, we can only run tests in one workflow on each Mac mini, which is wasteful. Also, the cluster will not be displayed in the Selenoid UI. Iteration #2: GGR→Selenoid→Appium Selenoid allows you to work . The above problems informed our decision to use Selenoid when running iOS tests as well, though as an executable file: with more than just containers Download Selenoid ( / ). amd64 arm64 Create a configuration file. browsers.json Be sure to specify Appium and startup settings in the configuration file: {
  "iPhone 14": {
    "default": "16.2",
    "versions": {
      "16.2": {
        "image": ["appium", "--log-timestamp", "--log-no-colors", ...]
      }
    }
  }
} Give permission to execute the Selenoid file. In our case, we used . chmod 755 Run Selenoid via the terminal. We used the following parameters: . selenoid -conf ~/browsers.json -disable-docker -capture-driver-logs -service-startup-timeout 4m -session-attempt-timeout 4m -timeout 6m -limit 2 The specified timeouts are necessary because standard timeouts may not be sufficient for downloading the app from the cloud storage and launching the simulator. The parameter was used to set the maximum number of running simulators. This is the reference value to be used by the GGR in the future. The performance of the host is used as a guide for setting the parameter. -limit You can read more about startup settings in the Selenoid . documentation If need be, a PLIST file can be created on each Mac mini to autorun Selenoid in case of a sudden system restart. Now, the process of the cluster looks like this: With this approach, we partially achieve Selenoid UI functionality and the ability to run tests across multiple flows on the same host. The downside is that, on each Mac mini, you have to manually carry out a multitude of routine tasks to create a simulator and link it with Appium by specifying the UUID and port assignment. This can become a problem if you need to upgrade to a new iOS version later. Iteration #3: GGR→Selenoid→Bash→Appium We have a large Mac mini farm that will continue growing as time goes on. With this in mind, we were looking for a way to make scaling easier so that we wouldn’t have to create simulators by hand and then connect them to Appium. With the previous schema in place, Appium and simulators would have had long lifetimes, which could have led to unpredictable consequences. Searching for a solution, we discovered that a bash script can be specified as a host in the Selenoid configuration file: {
  "iPhone 14": {
    "default": "16.2",
    "versions": {
      "16.2": {
        "image": ["~/bin/config/start_appium.sh", "iPhone 14"]
      }
    }
  }
} This is what ours looks like: #!/bin/bash

set -ex

DEVICE_NAME=$1
APPIUM_PORT=$(echo $2 | cut -d '=' -f 2)

function clean() {
  if [ -n "$APPIUM_PID" ]; then
      kill -TERM "$APPIUM_PID"
  fi
  if [ -n "$DEVICE_UDID" ]; then
      xcrun simctl delete $DEVICE_UDID
  fi
}

trap clean SIGINT SIGTERM

# Each simulator has a udid, so to run the same devices in parallel - clone and run
# only clones. You cannot clone a running device. After closing the session, delete the clone.
cloned_device_name="[APPIUM] ${DEVICE_NAME} ($(date +%Y%m%d%H%M%S))"
DEVICE_UDID=$(xcrun simctl clone "$DEVICE_NAME" "$cloned_device_name")

# https://github.com/appium/appium-xcuitest-driver#important-simulator-capabilities
WDA_LOCAL_PORT=$(($APPIUM_PORT+1000))
MJPEG_SERVER_PORT=$(($WDA_LOCAL_PORT+1000))
DEFAULT_CAPABILITIES='"appium:udid":"'$DEVICE_UDID'","appium:automationName":"'XCUITest'","appium:wdaLocalPort":"'$WDA_LOCAL_PORT'","appium:mjpegServerPort":"'$MJPEG_SERVER_PORT'"'

appium --base-path=/wd/hub --port=$APPIUM_PORT --log-timestamp --log-no-colors --allow-insecure=get_server_logs,adb_shell \
       --allow-cors --log-timestamp --log {choose_directory_for_logs} \
       --default-capabilities "{$DEFAULT_CAPABILITIES}" &
APPIUM_PID=$!

wait If the script is used, pay close attention to the stated capabilities and Appium startup settings. These are set up here assuming that Appium 2.x is used for the run ‒ Appium 1.x does not require the vendor to be specified in capabilities, and there is no option of specifying --base-pat. The script solves the problem of simulators running in parallel: When multiple Appiums are directly connected to GGR from one Mac mini, , because you cannot run the same emulator with identical UDIDs. You have to manually duplicate and hardcode the UDID each and every time. (For example, if you need to change the iOS version or the simulator model.) a problem arises with the emulators . It is necessary to run Appium manually every time, and regularly check it for conflicts with ports and simulators. Poor scalability The use of Selenoid makes it possible to simplify this process down to a single script that does not create conflicts between multiple Appium + Simulator pairs within a single host. It launches Appium and kills it when receiving a corresponding signal from Selenoid, and it dynamically clones the simulators at startup and deletes them once the session ends. The process we developed looks like this: Next, we add the Selenoid addresses of each Mac mini to the configuration file of the deployed GGR, merging the Android and iOS structures: Bottom-line summary The assembled infrastructure allows us to run a total of about 500 UI tests per hour across 36 workflows on both platforms. Addition of a new host for Android tests can be fully automated by using the workflow on GitHub Actions, and takes about two minutes. In the very near future, we plan to automate the deployment of the Selenoid cluster on a Mac mini as well. Further down the road, we would like to try out running containers on a Mac mini with Linux to unify all the processes and make it easier to deploy to them without breaking any MacOS usage rules. If you have had any related experience, we'd love for you to share it in the comments. Docker-OSX Posted by . Ivan Grigoriev

How to Run 5000+ Tests on Mobile Devices Everyday; From inDrive's Playbook (Part 2)

কিভাবে প্রতিদিন মোবাইল ডিভাইসে 5000+ পরীক্ষা চালাবেন; ইনড্রাইভের প্লেবুক থেকে (পর্ব 2)

So führen Sie täglich über 5000 Tests auf Mobilgeräten durch; Aus dem Playbook von inDrive (Teil 2)

매일 모바일 장치에서 5000개 이상의 테스트를 실행하는 방법 inDrive의 플레이북(2부)에서

Her Gün Mobil Cihazlarda 5000'den Fazla Test Nasıl Çalıştırılır; inDrive'ın Başucu Kitabı'ndan (Bölüm 2)

Hi all! My name is Taras Egorov; I'm an engineer at inDrive. I'll show you how we set up an infrastructure capable of running more than 5,000 tests per day on iOS and Android devices combined. The secret is simple: we used Selenoid. Preface Last year, our colleagues conducted a study of auto testing, and we took part in a survey as part of the study. We were pleased with the survey's findings, so we decided to write an article to share our experience with you and get some advice in return. We thought it a good idea to divide the material into two parts: the first one focusing on Android and the second on iOS. Let's begin with Android. Running the tests on Android Selenoid is a tool for running and managing browsers and Android emulators in a Docker container. You can read more about this . popular in the documentation To write Appium tests, we use: Kotlin; JUnit 5; Maven. The first run. Setting up Selenoid Create a config file: browsers.json {

  "android": {

    "default": "10.0",

    "versions": {

      "10.0": {

        "image": "browsers/android:10.0",

        "port": "4444",

        "path": "/wd/hub"

      }

    }

  }

} The emulator image is specified in . The guys from have prepared ready-made images of Android emulators. You can check them out or . The images don't differ from each other in any way. image aerokube here here Let’s take the image as an example. The image must be downloaded beforehand: , otherwise the tests will not run: browsers/android:10.0 docker pull browsers/android:10.0 Original error: create container: Error response from daemon: No such image: browsers/android:10.0 The next step is to run Selenoid. We do that directly via , or there’s the option of using . docker Configuration Manager docker run -d \

           -v /var/run/docker.sock:/var/run/docker.sock \

           -v "$(pwd)/selenoid/config/":/etc/selenoid/:ro \

           -p 4444:4444 \

           --name selenoid \

           aerokube/selenoid:1.10.7 You can check to see if Selenoid is working properly by following the link in your browser: http://localhost:4444 You are using Selenoid 1.10.7! Specify the Selenoid address in the Appium tests in the driver: ...
val driver = AndroidDriver(URL("http://localhost:4444/wd/hub"), capabilities)
... Next, specify the link to the build in capabilities: ... 
capabilities.setCapability("appium:app", "https://storage.example.com/builds/app.apk")
... If unable to provide a link, you can specify the path to the build:** ...
capabilities.setCapability("appium:app", "/builds/app.apk")
... Where is the path inside the container where the emulator is being run. For this option to work properly, be sure to specify the in : /builds/app.apk volumes browsers.json {

  "android": {

    "default": "10.0",

    "versions": {

      "10.0": {

        ...

        "volumes": [

          "/home/username/app.apk:/builds/app.apk:ro"

        ]

        ...

      }

    }

  }

} Where is the path to the build on the host platform. /home/username/app.apk That's it, we've almost set up Selenoid, and now we can try running the tests: ./mvnw test But, unfortunately, the tests will not be able to run. Let's look into this and see what's wrong. The second run. Taking a look at the logs and video The first thing to do after a failed startup is to check out the Selenoid logs: docker logs selenoid [INIT] [Loading configuration files...]
[INIT] [Loaded configuration from /etc/selenoid/browsers.json]
[INIT] [Video Dir: /opt/selenoid/video]
[INIT] [Your Docker API version is 1.41]
[INIT] [Timezone: UTC]
[INIT] [Listening on :4444]
[NEW_REQUEST] [unknown] [172.17.0.1]
[NEW_REQUEST_ACCEPTED] [unknown] [172.17.0.1]
[LOCATING_SERVICE] [android] [10.0]
[USING_DOCKER] [android] [10.0]
[CREATING_CONTAINER] [selenoid/android:10.0]
[STARTING_CONTAINER] [selenoid/android:10.0] [75e454341da7fc4b58ba104a5180813bac6cd7c124037a759b6c976e65b168fa]
[CONTAINER_STARTED] [selenoid/android:10.0] [75e454341da7fc4b58ba104a5180813bac6cd7c124037a759b6c976e65b168fa] [0.40s]
[0] [REMOVING_CONTAINER] [75e454341da7fc4b58ba104a5180813bac6cd7c124037a759b6c976e65b168fa]
[0] [CONTAINER_REMOVED] [75e454341da7fc4b58ba104a5180813bac6cd7c124037a759b6c976e65b168fa]
[0] [SERVICE_STARTUP_FAILED] [http://172.17.0.3:4444/wd/hub does not respond in 30s] We see that the status is SERVICE_STARTUP_FAILED. Go to the and look at the status value: documentation SERVICE_STARTUP_FAILED - Failed to start Docker container or driver binary The error doesn’t tell you much, and more information is required. It would be good to take a look at the container logs. Let's do that by enabling logging: docker run -d \

           -p 4444:4444 \

           -v /var/run/docker.sock:/var/run/docker.sock \

           -v "$(pwd)/selenoid/config/":/etc/selenoid/:ro \

           -v  "$(pwd)/selenoid/logs/":/opt/selenoid/logs/ \

           aerokube/selenoid:1.10.7 \

           -log-output-dir /opt/selenoid/logs We also enable logs in the Capabilities section: ...
capabilities.setCapability("enableLog", true)
... Run the tests and review the logs using the browser : http://localhost:4444/logs/ 2023-04-16T13:44:43.909768530Z Waiting X server...
2023-04-16T13:44:44.009494775Z Logging to: /tmp/fluxbox.log
2023-04-16T13:44:44.047587277Z Waiting X server...
2023-04-16T13:44:44.151933325Z Waiting X server...
2023-04-16T13:44:44.262850410Z * daemon not running; starting now at tcp:5037
2023-04-16T13:44:44.457972956Z * daemon started successfully
2023-04-16T13:44:44.458249266Z adb: no devices/emulators found
2023-04-16T13:44:45.463480812Z adb: no devices/emulators found
2023-04-16T13:44:46.471547723Z adb: no devices/emulators found
2023-04-16T13:44:47.476093515Z adb: no devices/emulators found
2023-04-16T13:44:48.481987351Z adb: no devices/emulators found
2023-04-16T13:44:49.486503149Z adb: no devices/emulators found
2023-04-16T13:44:50.492757801Z adb: no devices/emulators found
2023-04-16T13:44:51.499094108Z adb: no devices/emulators found
2023-04-16T13:44:52.505862428Z adb: no devices/emulators found
2023-04-16T13:44:53.513276412Z adb: no devices/emulators found
2023-04-16T13:44:54.520642210Z adb: no devices/emulators found
2023-04-16T13:44:55.527420189Z adb: no devices/emulators found
2023-04-16T13:44:56.534631013Z adb: no devices/emulators found
2023-04-16T13:44:57.316094939Z WARNING. Using fallback path for the emulator registration directory.
2023-04-16T13:44:57.335415397Z checkValid: hw configs not eq
2023-04-16T13:44:57.541959741Z adb: device offline
2023-04-16T13:44:58.547907700Z adb: device offline
2023-04-16T13:44:58.565504866Z emulator: WARNING: System image is writable
2023-04-16T13:44:58.565528396Z emulator: Cold boot: different AVD configuration
2023-04-16T13:44:58.565532576Z Your emulator is out of date, please update by launching Android Studio:
2023-04-16T13:44:58.565536346Z  - Start Android Studio
2023-04-16T13:44:58.565539506Z  - Select menu "Tools > Android > SDK Manager"
2023-04-16T13:44:58.565543076Z  - Click "SDK Tools" tab
2023-04-16T13:44:58.565546216Z  - Check "Android Emulator" checkbox
2023-04-16T13:44:58.565549216Z  - Click "OK"
2023-04-16T13:44:58.565552146Z 
2023-04-16T13:44:59.554451514Z adb: device offline
2023-04-16T13:45:00.560926060Z adb: device offline
2023-04-16T13:45:01.568777440Z adb: device offline
2023-04-16T13:45:12.124226047Z emulator: INFO: boot completed
2023-04-16T13:45:12.124251007Z emulator: INFO: boot time 27848 ms
2023-04-16T13:45:12.124255077Z emulator: Increasing screen off timeout, logcat buffer size to 2M.
2023-04-16T13:45:12.152557294Z emulator: Revoking microphone permissions for Google App. The container logs are not much help here either, because you can't see the Appium logs. Now let's try to enable them. To do this, let's look at the script : entry point.sh ...
if [ -z "$VERBOSE" ]; then
    APPIUM_ARGS="$APPIUM_ARGS --log-level error"
else
    EMULATOR_ARGS="$EMULATOR_ARGS -verbose"
fi
... To enable Appium logs, the parameters and : must be passed to the container: VERBOSE=true APPIUM_ARGS=--log-level debug {

  "android": {

    "default": "10.0",

    "versions": {

      "10.0": {

        ...

        "env": [

          "VERBOSE=true",

          "APPIUM_ARGS=--log-level debug"

        ]

        ...

      }

    }

  }

} To enable Appium to debug logs, you need to pass VERBOSE; in this case, the emulator logs turn on and start filling the "ether"” But we fixed that for future images =) Now it is enough to pass to . APPIUM_ARGS=-log-level debug ...
[HTTP] --> POST /wd/hub/session/c89fa9c2-ca2b-49cd-ab31-590eeccf77d1/element
[HTTP] {"using":"id","value":"authorization_edittext_phone"}
[debug] [W3C (c89fa9c2)] Calling AppiumDriver.findElement() with args: ["id","authorization_edittext_phone","
c89fa9c2-ca2b-49cd-ab31-590eeccf77d1"]
[debug] [BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, -and
roid uiautomator
[debug] [BaseDriver] Waiting up to 0 ms for condition
[debug] [WD Proxy] Matched '/element' to command name 'findElement'
[debug] [WD Proxy] Proxying [POST /element] to [POST http://127.0.0.1:8200/wd/hub/session/65943f03-3b35-4d3eb221-d6dc7988f935/element] with body: {"strategy":"id","selector":
"authorization_edittext_phone","context":"","multiple":false}
[WD Proxy] Got response with status 404: {"sessionId":"65943f03-3b35-4d3e-b221-d6dc7988f935","value":{"error"
:"no such element","message":"An element could not be located on the page using the given search parameters","stacktrace":"io.appium.uiautomator2.common.exceptions.El
ementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(Find
Element.java:73)\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(SafeRequestHandler.java:41)\n\tat io.appium.uiautomator2.server.AppiumServlet.
handleRequest(AppiumServlet.java:253)\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(AppiumServlet.java:247)\n\tat io.appium.uiautomator2.http.Se
rverHandler.channelRead(ServerHandler.java:68)\n\tat io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)\n\tat io
.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)\n\tat io.netty.chann...
[debug] [W3C] Matched W3C error code 'no such element' to NoSuchElementError
[debug] [W3C (c89fa9c2)] Encountered internal error running command: NoSuchElementError: An element could not
be located on the page using the given search parameters.
[debug] [W3C (c89fa9c2)]     at AndroidUiautomator2Driver.findElOrEls (/opt/node_modules/appium/node_modules/appium-android-driver/lib/commands/find.js:75:11)
[debug] [W3C (c89fa9c2)]     at process._tickCallback (internal/process/next_tick.js:68:7)
[HTTP] <-- POST /wd/hub/session/c89fa9c2-ca2b-49cd-ab31-590eeccf77d1/element 404 23 ms - 444
... As seen from the logs, Appium cannot find our element. Let's see what is happening on the emulator screen. To do this, we have to run the Selenoid UI: docker run -d \

           --name selenoid-ui \

           -p 8080:8080 \

           --link selenoid:selenoid \

           aerokube/selenoid-ui:1.10.4 \

           --selenoid-uri "http://selenoid:4444" Go to and open the Selenoid UI: http://0.0.0.0:8080 Be sure to enable VNC and video recording in the tests: ...

capabilities.setCapability("enableVNC", true)

capabilities.setCapability("enableVideo", true)

... The Selenoid startup command ends up looking like this: docker run -d \

-v /var/run/docker.sock:/var/run/docker.sock \

-v "(pwd)/selenoid/logs/":/opt/selenoid/logs/ \

-v /opt/selenoid/video/:/opt/selenoid/video/ \

-e OVERRIDE_VIDEO_OUTPUT_DIR="/opt/selenoid/video/" \

-p 4444:4444 \

-name selenoid \

aerokube/selenoid:1.10.7 \

-log-output-dir /opt/selenoid/logs Open the Selenoid UI once the tests are up and running: And here's . a video of it https://www.youtube.com/watch?v=Hm7s5ZjnVYQ&embedable=true We found the cause of the startup error. Great! Let’s move on. The third run. Building an emulator image As it turns out, the images of Selenoid emulators won’t work without Google Play services. To remedy this situation, you must build an emulator image yourself. The guys from aerokube have assembled everything you need for this: and . a repository with photos documentation the repository. Downloading Go to the folder. selenium Run the script and answer the questions. This is what it looks like in our case: ./automate_android.sh Specify Appium version: [1.18.1]

>> 1.18.1

Specify Android image type (possible values: "default", "google_apis", "google_apis_playstore", "android-tv", "android-wear"): [default]

>> google_apis

Specify Application Binary Interface (possible values: "armeabi-v7a", "arm64-v8a", "x86", "x86_64"): [x86]

>> x86

Specify Android version: [8.1]

>> 10.0

Specify device preset name if needed (e.g. "Nexus 4"):

>>

Specify SD card size, Mb: [500]

>>

Specify userdata.img size, Mb: [500]

>>

Are you building a Chrome Mobile image (for mobile web testing): [n]

>> y

Specify Chromedriver version if needed (required for Chrome Mobile):

>> 74.0.3729.6

Specify image tag: [selenoid/chrome-mobile:74.0]

>> android-emulator:10.0

Add Android quick boot snapshot? [y]

>> n When I saw the question Add Android quick boot snapshot?, I thought it was an emulator . But if you look at the , it calls a , which is needed to install APK applications. Basically, it doesn't give us any gain. snapshot code script We already use snapshot emulators , but we'll talk about that in other articles. to speed up container launches Once the image is built, we will be prompted to push it into the registry. Since we don't need that yet, we will kindly decline the offer: Push?  >> n We have put together a build with Google Play services. Remember to change the image parameter in browsers.json, and restart Selenoid. Now let's try rerunning the tests: [INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------ And of the test run. here’s a video https://www.youtube.com/watch?v=w-uzB7hg7g8&t=1s&embedable=true To sum up What we have done: Configured Selenoid to run Android tests. Learned how to check out the logs and videos to troubleshoot. Built our own emulator image with Google Play services. Something else I would like to tell you about: Selenoid timeouts. If your app is large, you might run into problems with timeouts. How we tried making the container run faster. The video shows that the run takes about a minute or so. How we tried running native Android tests written in Espresso on Selenoid. Spoiler alert: this works! Meanwhile, in the next part, we'll tell you how we scaled up the infrastructure and ran tests on iOS.

How to Run 5000+ Tests on Mobile Devices Everyday; From inDrive's Playbook (Part 1)

কিভাবে প্রতিদিন মোবাইল ডিভাইসে 5000+ পরীক্ষা চালাবেন; ইনড্রাইভের প্লেবুক থেকে (পর্ব 1)

So führen Sie täglich über 5000 Tests auf Mobilgeräten durch; Aus dem Playbook von inDrive (Teil 1)

Cómo ejecutar más de 5000 pruebas en dispositivos móviles todos los días; Del libro de jugadas de InDrive (Parte 1)

Comment exécuter plus de 5 000 tests sur des appareils mobiles au quotidien ; Du Playbook d'InDrive (Partie 1)

मोबाइल उपकरणों पर प्रतिदिन 5000+ परीक्षण कैसे करें; इनड्राइव की प्लेबुक से (भाग 1)

モバイルデバイスで毎日 5000 件以上のテストを実行する方法; InDrive のプレイブックより (パート 1)

매일 모바일 장치에서 5000개 이상의 테스트를 실행하는 방법 inDrive의 플레이북(1부)에서

Como executar mais de 5.000 testes em dispositivos móveis todos os dias; Do manual do InDrive (parte 1)

Her Gün Mobil Cihazlarda 5000'den Fazla Test Nasıl Çalıştırılır; inDrive'ın Başucu Kitabı'ndan (Bölüm 1)

Cách chạy hơn 5000 bài kiểm tra trên thiết bị di động mỗi ngày; Từ Playbook của InDrive (Phần 1)

如何每天在移动设备上运行 5000 多个测试；来自 InDrive 的剧本（第 1 部分）

The Surprising Link Between Cybersecurity Incidents and SEO

সাইবারসিকিউরিটি ঘটনা এবং সিইওর মধ্যে আশ্চর্যজনক লিঙ্ক

Der überraschende Zusammenhang zwischen Cybersicherheitsvorfällen und CEO

El sorprendente vínculo entre los incidentes de ciberseguridad y el director ejecutivo

Le lien surprenant entre les incidents de cybersécurité et le PDG

साइबर सुरक्षा घटनाओं और सीईओ के बीच आश्चर्यजनक संबंध

サイバーセキュリティインシデントとCEOの意外な関係

사이버 보안 사고와 CEO 사이의 놀라운 연관성

A ligação surpreendente entre incidentes de segurança cibernética e CEO

Удивительная связь между инцидентами в области кибербезопасности и генеральным директором

Siber Güvenlik Olayları ile CEO Arasındaki Şaşırtıcı Bağlantı

Mối liên hệ đáng ngạc nhiên giữa sự cố an ninh mạng và CEO

网络安全事件与 CEO 之间的惊人联系

What Will the Spring of Technology Bring? Part 2 — Virtual Human

INDRIVE

indriver.com

1K-5K employees

Since 2020

COMPANY RANKING

INDRIVE

EVERGREEN INDEX #5725

Representing this company? Click here to claim and customize this page!

inDrive WIKI

INDRIVE

indriver.com

1K-5K employees

Since 2020

COMPANY RANKING

INDRIVE

EVERGREEN INDEX #5725

HACKERNOON STORIES ON INDRIVE

RELATED COMPANIESRANK

Representing this company? Click here to claim and customize this page!

inDrive WIKI