One of the main business needs was to accelerate the process of package pickup. Especially during holiday seasons, when the number of orders and the demand for lockers is much higher.

Remote locker opening can reduce the lines in front of Parcel Lockers and also it leaves out the verification process (from the perspective of the user, of course) which requires entering or scanning a barcode. during holiday seasons, when the number of orders and the demand for lockers is much higher.

Another important goal was to entirely give up text messages with parcel pickup codes.

This solution was highly ineffective cost-wise (InPost was sending tens of millions text messages monthly!) and also was risky in terms of potential frauds.

By allowing the users to collect their packages more seamlessly and quickly, InPost can deliver even more parcels every day!

The functionality has been shared with the app’s version 2 release. The process of parcel collection needed to be fully intuitive and similar in both InPost mobile app and Parcel Lockers.

The process of remote parcel locker opening is designed precisely not to interrupt the Client’s system.

The functionality was highly praised by the users, contributing to their everyday convenience.

Effective optimization of the process of picking up the parcels from lockers.

The solution resulted in a larger number of free lockers for other clients that made an order using the InPost services. Usually, when the lockers were overstuffed, the courier had to park in front of the Parcel Locker and it took a couple of hours to hand the packages over to the customers.

With MultiLocker, the effectiveness of the whole system grows, as the delivery person can put a couple of packages ordered by one person in a single locker.

Posting parcels using the InPost app is the first service of this kind available on the market. This functionality has been released with the new app’s 3.0.0 version.

The new feature’s goal was to maximally facilitate the process of posting the packages:

Along with the Client, we thoroughly analyzed the project, established the highest priorities and the order of individual functionalities implementation.

Workshops resulted in preparing the application’s prototype assessed internally by the InPost team.

It included basic, most essential features that needed to be developed in the future.

After creating the second prototype (based on MVP), we designed the UX to track shipments as well as other side components of the application.

We chose only the ones that fully represented our Client’s business value. Although at this point the structure of the app remained unchanged, we redesigned it according to the company’s brand book, including color consistency and the use of new fonts.

Downloading a new version of the app from the store is connected with reading the HTML code. If an app store introduces even a small
change, the app’s functionalities may stop working and the level of
security may drop.

To avoid the risk, we decided to use API needing to implement some
adjustments on the backend side. Version 3 of the app was released in 2020 and introduced InPost Mobile to Huawei App Gallery.

In the app’s first version, API has been based on the mocks which simulate the target functionality. After the development, it became clear that it required rebuilding.

We solved it differently in the version 2 of the app. API was ready before the functionalities were made or during development. This way we were able to avoid time delays in the project.

We had to minimise the risk of handing over the parcel to a wrong user.

When a user wants to collect a package remotely, the app sends a request with parcel’s number, pickup code and device location (within a certain range) to the system. If the verification is successful, the session opens up, and if not, the session is rejected.

The solution suggested by InPost required a demanding process of programming. We had to face all the potential difficulties it came with.

First, we had to calculate the time for each step in milliseconds instead of using time frames. This way the app receives the times, verifies and converts them to the local time, and then passes them between classes that are responsible for locker opening.

Now, the time spent on the screen is added to the current hour. If the locker opening request is confirmed by the app, the next actions are taken by the Parcel Locker.

Each machine has its own computer connected to the InPost system being able to take care of each step and properly send the data.

Firstly, remote Parcel Locker opening was based on sending requests to ask the API about the status of the locker. But it came with a risk.

The requests we sent every second so the system would make sure that the locker door is open. But this solution was highly problematic, especially during so-called “peak” moments, e.g. during holidays when the demand for package delivery rapidly grows. Too many requests per second could cause an overload of the InPost systems bugging or stopping them completely.

We’ve decided that the request should be blocked by InPost until the locker’s status changes (possible options being “open”, “fail” or “timeout”). The whole process is very quick but it requires extending HTTP timeouts. The default time for the whole app is 10 seconds. In this case, we needed to create a separate API configuration so the timeout for one request can take 30 seconds. It was the easiest solution to avoid the system’s overload.

If a package is taken out of the locker and the door are being locked, a user can click the button confirming the operation – then the app sends a request to InPost’s API with a message that the doors are locked. But what if they aren’t?

The fix was quite simple. After clicking the “Parcel taken out” button, the app shows a screen with the “Door closed” announcement. It doesn’t send an API request and goes straight to the summary. This way, a user isn’t blocked on one screen – especially when the door is damaged and can’t be closed.

At this point, after summarizing the process, a user has an option to send a complaint, for example when the package has defects.

The solution was fast and simple but it couldn’t allow users to open the locker from their home when their significant other is passing by the Parcel Locker and wants to pick up their package. We needed the app to verify the distance between the person collecting a parcel and the locker.

We wanted to avoid the situation in which the app says that the client is not actually near the locker.

The first tested solution was to drag the last known phone location, but this method wasn’t efficient though. After checking the logs, it appeared that the localization could be determined using data from a couple of minutes earlier which was interpreted by the system as being too far from the Parcel Locker. At this point, the app wouldn’t agree to open the locker remotely.

It’s usually applied in apps that don’t have any navigation requirements and don’t need very detailed data. Unfortunately, tests done by InPost showed that this mode is not enough – it located the device within 100 meters or more and in this case, a user had to be closer than 100 meters.

In the next step, we decided to use the high accuracy mode of
localization which might have required special settings in the device system if the localization accuracy changed. Using this information (technical launch of Intent) will open system dialogue which will allow it to automatically change the localization accuracy.

It is worth remembering that the highest accuracy depends on GPS signals which mean it works best outside. The localization process can take more time when the signal is distracted. In this case, the system will send information (Exception) to the app which will fix the issue (Intent).

Procedure was carried out following the list of the most important functionalities. Testers from iteo and InPost went through each point before releasing subsequent versions of the application.

There were also manual field tests at the Parcel Lockers.

InPost application won main prize at Mobile Trends Awards and became the app of the year 2019. It was recognized in the ‘Service’ category also as no 1. The company repeated its success in 2020 as well, winning the main award, 1st place in the ‘Service’ category, and 2nd place in users’ voting.

The app has now over 5M downloads with daily dynamic increase due to huge demand for indirect goods delivery and collection. All versions of the application remained on first positions in Polish Google and Apple stores for a long time.

The company needed us once again. This time, along with creating the new Rossmann Club mobile application, there was a need of building a new version of the app’s home screen (Dashboard) as well as a set of dedicated cards.

The goal was to make the app’s Dashboard visually appealing, easy, and convenient to use, allowing a smooth transition between two of the applied modes: At home and In store. Every mode needed to have its own looks and prioritize different functionalities.

Additional task was to personalize the app’s view depending on the parameters assigned to a target user. The views had to be compatible with both iOS and Android systems and available for all the users – whether logged in or not.

It was also necessary to design a new CMS module which would allow managing the Dashboard and cards according to the business’s requirements.

First, we download the list of texts for the cards with a single request and they are displayed. The cards have many different data: from graphics to the list of products. Other requests for details are queued and sorted depending on which elements of the list are visible. In the end, the data is joined to a current card’s list. It keeps the list fluent, appears immediately, and the users always see the data of the cards they are presently looking at.

Products on the card can be displayed in many different arrangements on the 2:2 net – every arrangement is a separate scene and transformation between the scenes is launched in the form of animation. It allows a fluent change of deploying the graphics.

There can be many cards on the list and their graphics usually take up the whole card. Additionally, a graphic can be a static picture or a gif. They have to be stored in the memory to avoid downloading them every time anew.

From time to time, there’s also a need for a thumbnail or an alternative graphic. What responds to all of these needs is a Glide
library – and we squeezed it till the last drop!

Data which won’t change their value, e.g. graphics, are saved in the read-only memory of the app. If a graphic is repeated, it’s not
processed from the internet once again but loaded directly from the storage. Data that can be changed are more difficult to store.

The solution is caching them in the RAM of the device. A user is always provided with valid data within the limits of a single session
with the app. After launching it once more, data is updated.

We provided both by an animation based on a user’s actions. We’ve decided to animate the scrolling of the list. Thanks to the dynamic cards’ sliding in regard to the speed of the move, a user gets an impression that the tiles are floating and bouncing off the edge which gives a natural visual response. Applying the physics was extremely important for the most natural floating behaviour.

We operated simultaneously in two different teams and had to clip it all together in a quite short period of time. Although we created only a small piece of the whole mobile app, it was highly interrelated with
Rossmann’s development process and in result difficult to deploy. Even though it affected the backend, too, it was much easier to implement thanks to the applied microservice architecture

Functional tests were based on the guidelines provided by the client and information acquired during the team interview. We also performed exploratory tests, retests, and regression tests on different internet browsers and mobile devices’ system versions. The acceptance tests were applied by the Client.

The application has more than 10M downloads on Google Play and is used everyday for both offline and online shopping, making the process easier and more convenient. It works flawlessly on Android and iOS based devices and a dedicated CMS allows a seamless Dashboard and cards management, targeting a client’s needs and following the company’s requirements.

One of the main business needs was to accelerate the process of package pickup. Especially during holiday seasons, when the number of orders and the demand for lockers is much higher.

Remote locker opening can reduce the lines in front of Parcel Lockers and also it leaves out the verification process (from the perspective of the user, of course) which requires entering or scanning a barcode. during holiday seasons, when the number of orders and the demand for lockers is much higher.

Another important goal was to entirely give up text messages with parcel pickup codes.

This solution was highly ineffective cost-wise (InPost was sending tens of millions text messages monthly!) and also was risky in terms of potential frauds.

After creating the second prototype (based on MVP), we designed the UX to track shipments as well as other side components of the application.

We chose only the ones that fully represented our Client’s business value. Although at this point the structure of the app remained unchanged, we redesigned it according to the company’s brand book, including color consistency and the use of new fonts.

One of the main business needs was to accelerate the process of package pickup. Especially during holiday seasons, when the number of orders and the demand for lockers is much higher.

Remote locker opening can reduce the lines in front of Parcel Lockers and also it leaves out the verification process (from the perspective of the user, of course) which requires entering or scanning a barcode. during holiday seasons, when the number of orders and the demand for lockers is much higher.

Another important goal was to entirely give up text messages with parcel pickup codes.

This solution was highly ineffective cost-wise (InPost was sending tens of millions text messages monthly!) and also was risky in terms of potential frauds.

One of the main business needs was to accelerate the process of package pickup. Especially during holiday seasons, when the number of orders and the demand for lockers is much higher.

Remote locker opening can reduce the lines in front of Parcel Lockers and also it leaves out the verification process (from the perspective of the user, of course) which requires entering or scanning a barcode. during holiday seasons, when the number of orders and the demand for lockers is much higher.

Another important goal was to entirely give up text messages with parcel pickup codes.

This solution was highly ineffective cost-wise (InPost was sending tens of millions text messages monthly!) and also was risky in terms of potential frauds.

By allowing the users to collect their packages more seamlessly and quickly, InPost can deliver even more parcels every day!

The functionality has been shared with the app’s version 2 release. The process of parcel collection needed to be fully intuitive and similar in both InPost mobile app and Parcel Lockers.

The process of remote parcel locker opening is designed precisely not to interrupt the Client’s system.

The functionality was highly praised by the users, contributing to their everyday convenience.

Effective optimization of the process of picking up the parcels from lockers.

The solution resulted in a larger number of free lockers for other clients that made an order using the InPost services. Usually, when the lockers were overstuffed, the courier had to park in front of the Parcel Locker and it took a couple of hours to hand the packages over to the customers.

With MultiLocker, the effectiveness of the whole system grows, as the delivery person can put a couple of packages ordered by one person in a single locker.

Posting parcels using the InPost app is the first service of this kind available on the market. This functionality has been released with the new app’s 3.0.0 version.

The new feature’s goal was to maximally facilitate the process of posting the packages:

Along with the Client, we thoroughly analyzed the project, established the highest priorities and the order of individual functionalities implementation.

Workshops resulted in preparing the application’s prototype assessed internally by the InPost team.

After creating the second prototype (based on MVP), we designed the UX to track shipments as well as other side components of the application.

We chose only the ones that fully represented our Client’s business value. Although at this point the structure of the app remained unchanged, we redesigned it according to the company’s brand book, including color consistency and the use of new fonts.

One of the main business needs was to accelerate the process of package pickup. Especially during holiday seasons, when the number of orders and the demand for lockers is much higher.

Remote locker opening can reduce the lines in front of Parcel Lockers and also it leaves out the verification process (from the perspective of the user, of course) which requires entering or scanning a barcode. during holiday seasons, when the number of orders and the demand for lockers is much higher.

Another important goal was to entirely give up text messages with parcel pickup codes.

This solution was highly ineffective cost-wise (InPost was sending tens of millions text messages monthly!) and also was risky in terms of potential frauds.

By allowing the users to collect their packages more seamlessly and quickly, InPost can deliver even more parcels every day!

The functionality has been shared with the app’s version 2 release. The process of parcel collection needed to be fully intuitive and similar in both InPost mobile app and Parcel Lockers.

The process of remote parcel locker opening is designed precisely not to interrupt the Client’s system.

The functionality was highly praised by the users, contributing to their everyday convenience.

Effective optimization of the process of picking up the parcels from lockers.

The solution resulted in a larger number of free lockers for other clients that made an order using the InPost services. Usually, when the lockers were overstuffed, the courier had to park in front of the Parcel Locker and it took a couple of hours to hand the packages over to the customers.

With MultiLocker, the effectiveness of the whole system grows, as the delivery person can put a couple of packages ordered by one person in a single locker.

Posting parcels using the InPost app is the first service of this kind available on the market. This functionality has been released with the new app’s 3.0.0 version.

The new feature’s goal was to maximally facilitate the process of posting the packages:

Along with the Client, we thoroughly analyzed the project, established the highest priorities and the order of individual functionalities implementation.

Workshops resulted in preparing the application’s prototype assessed internally by the InPost team.

It included basic, most essential features that needed to be developed in the future.

After creating the second prototype (based on MVP), we designed the UX to track shipments as well as other side components of the application.

We chose only the ones that fully represented our Client’s business value. Although at this point the structure of the app remained unchanged, we redesigned it according to the company’s brand book, including color consistency and the use of new fonts.

One of the main business needs was to accelerate the process of package pickup. Especially during holiday seasons, when the number of orders and the demand for lockers is much higher.

Remote locker opening can reduce the lines in front of Parcel Lockers and also it leaves out the verification process (from the perspective of the user, of course) which requires entering or scanning a barcode. during holiday seasons, when the number of orders and the demand for lockers is much higher.

Another important goal was to entirely give up text messages with parcel pickup codes.

This solution was highly ineffective cost-wise (InPost was sending tens of millions text messages monthly!) and also was risky in terms of potential frauds.

Along with the Client, we thoroughly analyzed the project, established the highest priorities and the order of individual functionalities implementation.

Workshops resulted in preparing the application’s prototype assessed internally by the InPost team.

After creating the second prototype (based on MVP), we designed the UX to track shipments as well as other side components of the application.

We chose only the ones that fully represented our Client’s business value. Although at this point the structure of the app remained unchanged, we redesigned it according to the company’s brand book, including color consistency and the use of new fonts.

One of the main business needs was to accelerate the process of package pickup. Especially during holiday seasons, when the number of orders and the demand for lockers is much higher.

Remote locker opening can reduce the lines in front of Parcel Lockers and also it leaves out the verification process (from the perspective of the user, of course) which requires entering or scanning a barcode. during holiday seasons, when the number of orders and the demand for lockers is much higher.

Another important goal was to entirely give up text messages with parcel pickup codes.

This solution was highly ineffective cost-wise (InPost was sending tens of millions text messages monthly!) and also was risky in terms of potential frauds.

Along with the Client, we thoroughly analyzed the project, established the highest priorities and the order of individual functionalities implementation.

Workshops resulted in preparing the application’s prototype assessed internally by the InPost team.

It included basic, most essential features that needed to be developed in the future.

After creating the second prototype (based on MVP), we designed the UX to track shipments as well as other side components of the application.

We chose only the ones that fully represented our Client’s business value. Although at this point the structure of the app remained unchanged, we redesigned it according to the company’s brand book, including color consistency and the use of new fonts.

Downloading a new version of the app from the store is connected with reading the HTML code. If an app store introduces even a small
change, the app’s functionalities may stop working and the level of
security may drop.

To avoid the risk, we decided to use API needing to implement some
adjustments on the backend side. Version 3 of the app was released in 2020 and introduced InPost Mobile to Huawei App Gallery.

In the app’s first version, API has been based on the mocks which simulate the target functionality. After the development, it became clear that it required rebuilding.

We solved it differently in the version 2 of the app. API was ready before the functionalities were made or during development. This way we were able to avoid time delays in the project.

We had to minimise the risk of handing over the parcel to a wrong user.

When a user wants to collect a package remotely, the app sends a request with parcel’s number, pickup code and device location (within a certain range) to the system. If the verification is successful, the session opens up, and if not, the session is rejected.

The solution suggested by InPost required a demanding process of programming. We had to face all the potential difficulties it came with.

First, we had to calculate the time for each step in milliseconds instead of using time frames. This way the app receives the times, verifies and converts them to the local time, and then passes them between classes that are responsible for locker opening.

Now, the time spent on the screen is added to the current hour. If the locker opening request is confirmed by the app, the next actions are taken by the Parcel Locker.

Each machine has its own computer connected to the InPost system being able to take care of each step and properly send the data.

Firstly, remote Parcel Locker opening was based on sending requests to ask the API about the status of the locker. But it came with a risk.

The requests we sent every second so the system would make sure that the locker door is open. But this solution was highly problematic, especially during so-called “peak” moments, e.g. during holidays when the demand for package delivery rapidly grows. Too many requests per second could cause an overload of the InPost systems bugging or stopping them completely.

We’ve decided that the request should be blocked by InPost until the locker’s status changes (possible options being “open”, “fail” or “timeout”). The whole process is very quick but it requires extending HTTP timeouts. The default time for the whole app is 10 seconds. In this case, we needed to create a separate API configuration so the timeout for one request can take 30 seconds. It was the easiest solution to avoid the system’s overload.

If a package is taken out of the locker and the door are being locked, a user can click the button confirming the operation – then the app sends a request to InPost’s API with a message that the doors are locked. But what if they aren’t?

The fix was quite simple. After clicking the “Parcel taken out” button, the app shows a screen with the “Door closed” announcement. It doesn’t send an API request and goes straight to the summary. This way, a user isn’t blocked on one screen – especially when the door is damaged and can’t be closed.

At this point, after summarizing the process, a user has an option to send a complaint, for example when the package has defects.

InPost application won main prize at Mobile Trends Awards and became the app of the year 2019. It was recognized in the ‘Service’ category also as no 1. The company repeated its success in 2020 as well, winning the main award, 1st place in the ‘Service’ category, and 2nd place in users’ voting.

The app has now over 5M downloads with daily dynamic increase due to huge demand for indirect goods delivery and collection. All versions of the application remained on first positions in Polish Google and Apple stores for a long time.

One of the main business needs was to accelerate the process of package pickup. Especially during holiday seasons, when the number of orders and the demand for lockers is much higher.

Remote locker opening can reduce the lines in front of Parcel Lockers and also it leaves out the verification process (from the perspective of the user, of course) which requires entering or scanning a barcode. during holiday seasons, when the number of orders and the demand for lockers is much higher.

Another important goal was to entirely give up text messages with parcel pickup codes.

This solution was highly ineffective cost-wise (InPost was sending tens of millions text messages monthly!) and also was risky in terms of potential frauds.

Developed by Bode Miller is a scoring ranking with a baseline metric to evaluate the user’s performance based on
a personal survey and data acquired during actual skiing.

Allow users to track their individual speed, turns, pace, vertical, mileage, and G-force with every slide.

For successful development, quests are applied to the elements that need to be improved and are adjusted individually to the user’s abilities.

The app was integrated with a visual depiction of the skier’s position based on the gathered movement analysis and helping provide professional feedback.

It lets the users follow each other within the app depending on their location and personal privacy preferences. They can compare the results and challenge one another to boost their overall performance.

Developed by Bode Miller is a scoring ranking with a baseline metric to evaluate the user’s performance based on a personal survey and data acquired during actual skiing.

Swift allowed us to provide robust performance, seamless synchronization, and appealing design. The language is known for its speed and clean, safe code allowing us to create a spot-on product for iPhones.

Kotlin was our choice for Android. We used it for its concise code, safety, productivity, compatibility, and easy maintenance.

By allowing the users to collect their packages more seamlessly and quickly, InPost can deliver even more parcels every day!

The functionality has been shared with the app’s version 2 release. The process of parcel collection needed to be fully intuitive and similar in both InPost mobile app and Parcel Lockers.

The process of remote parcel locker opening is designed precisely not to interrupt the Client’s system.

The functionality was highly praised by the users, contributing to their everyday convenience.

Effective optimization of the process of picking up the parcels from lockers.

The solution resulted in a larger number of free lockers for other clients that made an order using the InPost services. Usually, when the lockers were overstuffed, the courier had to park in front of the Parcel Locker and it took a couple of hours to hand the packages over to the customers.

With MultiLocker, the effectiveness of the whole system grows, as the delivery person can put a couple of packages ordered by one person in a single locker.

Posting parcels using the InPost app is the first service of this kind available on the market. This functionality has been released with the new app’s 3.0.0 version.

The new feature’s goal was to maximally facilitate the process of posting the packages:

We developed dedicated sensors that can be connected to the SKEO app to provide better and more accurate analysis and UAR measurements. A very important aspect of this project was to keep modular, layered architecture, respecting the technology stack needed on each layer.

The project is built of modules written in native mobile languages to provide native access to low-level system interfaces. Application also integrates Unity modules and Algorithms written natively in C++.

The app supports customers using tablets which requires responsive app views behaviour. Depending on the device size, we automatically scale views to the specific screen size or, in special cases, rearrange view elements to make them more user friendly.

Along with the Client, we thoroughly analyzed the project, established the highest priorities and the order of individual functionalities implementation.

Workshops resulted in preparing the application’s prototype assessed internally by the InPost team.

Downloading a new version of the app from the store is connected with reading the HTML code. If an app store introduces even a small
change, the app’s functionalities may stop working and the level of
security may drop.

To avoid the risk, we decided to use API needing to implement some
adjustments on the backend side. Version 3 of the app was released in 2020 and introduced InPost Mobile to Huawei App Gallery.

In the app’s first version, API has been based on the mocks which simulate the target functionality. After the development, it became clear that it required rebuilding.

We solved it differently in the version 2 of the app. API was ready before the functionalities were made or during development. This way we were able to avoid time delays in the project.

We had to minimise the risk of handing over the parcel to a wrong user.

When a user wants to collect a package remotely, the app sends a request with parcel’s number, pickup code and device location (within a certain range) to the system. If the verification is successful, the session opens up, and if not, the session is rejected.

The solution suggested by InPost required a demanding process of programming. We had to face all the potential difficulties it came with.

First, we had to calculate the time for each step in milliseconds instead of using time frames. This way the app receives the times, verifies and converts them to the local time, and then passes them between classes that are responsible for locker opening.

Now, the time spent on the screen is added to the current hour. If the locker opening request is confirmed by the app, the next actions are taken by the Parcel Locker.

Each machine has its own computer connected to the InPost system being able to take care of each step and properly send the data.

Firstly, remote Parcel Locker opening was based on sending requests to ask the API about the status of the locker. But it came with a risk.

The requests we sent every second so the system would make sure that the locker door is open. But this solution was highly problematic, especially during so-called “peak” moments, e.g. during holidays when the demand for package delivery rapidly grows. Too many requests per second could cause an overload of the InPost systems bugging or stopping them completely.

We’ve decided that the request should be blocked by InPost until the locker’s status changes (possible options being “open”, “fail” or “timeout”). The whole process is very quick but it requires extending HTTP timeouts. The default time for the whole app is 10 seconds. In this case, we needed to create a separate API configuration so the timeout for one request can take 30 seconds. It was the easiest solution to avoid the system’s overload.

If a package is taken out of the locker and the door are being locked, a user can click the button confirming the operation – then the app sends a request to InPost’s API with a message that the doors are locked. But what if they aren’t?

The fix was quite simple. After clicking the “Parcel taken out” button, the app shows a screen with the “Door closed” announcement. It doesn’t send an API request and goes straight to the summary. This way, a user isn’t blocked on one screen – especially when the door is damaged and can’t be closed.

At this point, after summarizing the process, a user has an option to send a complaint, for example when the package has defects.

One of the main business needs was to accelerate the process of package pickup. Especially during holiday seasons, when the number of orders and the demand for lockers is much higher.

Remote locker opening can reduce the lines in front of Parcel Lockers and also it leaves out the verification process (from the perspective of the user, of course) which requires entering or scanning a barcode. during holiday seasons, when the number of orders and the demand for lockers is much higher.

Another important goal was to entirely give up text messages with parcel pickup codes.

This solution was highly ineffective cost-wise (InPost was sending tens of millions text messages monthly!) and also was risky in terms of potential frauds.

Existing applications of affiliates were rebuilt under the umbrella of SeePlaces. Customers are redirected to sections branded by cooperating local partners without leaving Itaka’s environment.

Along with the Client, we thoroughly analyzed the project, established the highest priorities and the order of individual functionalities implementation.

Workshops resulted in preparing the application’s prototype assessed internally by the InPost team.

It included basic, most essential features that needed to be developed in the future.

Downloading a new version of the app from the store is connected with reading the HTML code. If an app store introduces even a small
change, the app’s functionalities may stop working and the level of
security may drop.

To avoid the risk, we decided to use API needing to implement some
adjustments on the backend side. Version 3 of the app was released in 2020 and introduced InPost Mobile to Huawei App Gallery.

In the app’s first version, API has been based on the mocks which simulate the target functionality. After the development, it became clear that it required rebuilding.

We solved it differently in the version 2 of the app. API was ready before the functionalities were made or during development. This way we were able to avoid time delays in the project.

We had to minimise the risk of handing over the parcel to a wrong user.

When a user wants to collect a package remotely, the app sends a request with parcel’s number, pickup code and device location (within a certain range) to the system. If the verification is successful, the session opens up, and if not, the session is rejected.

The solution suggested by InPost required a demanding process of programming. We had to face all the potential difficulties it came with.

First, we had to calculate the time for each step in milliseconds instead of using time frames. This way the app receives the times, verifies and converts them to the local time, and then passes them between classes that are responsible for locker opening.

Now, the time spent on the screen is added to the current hour. If the locker opening request is confirmed by the app, the next actions are taken by the Parcel Locker.

Each machine has its own computer connected to the InPost system being able to take care of each step and properly send the data.