We&rsquo;re happy to bring to your attention the last part of the article series on using and adapting the Viper architecture.&nbsp;

The article about using and adapting the Viper architecture

The Use and Adaptation of the VIPER Architecture on Our Own Example of Development, part 4

In this blog post, we will consider various methods of how to find good developers and make your cooperation fruitful.
&nbsp;

Thinking about developing an application or site and need competent help? The first thing you should do is hire a software developer, and a good one ⭐ The task isn't easy and involves many difficulties. Read our article to find out the best way to get around all the pitfalls and to learn how to hire developers you can trust ✅ 

How to Find and Hire a Developer - Tactics that Work

Web projects testing is an extremely important procedure designed to ensure the smooth operation of the site; it helps to make your online platform work perfectly and without failures. But only multi-level testing performed by a qualified QA team would guarantee that the result of web developers' work meets all client's expectations.
In general, testing web projects includes a number of such stages as:
<ol dir="ltr">
<li style="text-align: justify;" role="presentation">Documentation testing</li>
<li style="text-align: justify;" role="presentation">Testing the layout</li>
<li style="text-align: justify;" role="presentation">Functional testing</li>
<li style="text-align: justify;" role="presentation">Testing usability</li>
<li style="text-align: justify;" role="presentation">Performance testing</li>
<li style="text-align: justify;" role="presentation">Security testing</li>
</ol>
<img src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/pictures/3960/content_content_testingtools2.jpg" alt="Web projects testing" width="800" height="681" />
In our article, we'd like to touch on the 2nd stage, namely, the layout testing.
We'll describe the whole process at length, discuss the pros and cons of each particular tool for such testing, and share our own practical experience.
<h2 dir="ltr" style="text-align: justify;">The basic logic of layout testing</h2>
First, let's talk about the sense of testing when it comes to the layout part. What is it and why is it needed?&nbsp;
Let&rsquo;s see!
The layout testing is aimed to search out noticeable inconsistencies in the website and includes the verification of the online resource scaling, resolution, reliability, and availability.
In addition, you should not forget another important issue, which is cross-browser ability.&nbsp;
<h3 dir="ltr" style="text-align: justify;">The cross-browser ability</h3>
As you know, we all have our own preferences in everything, including choosing the best browser to view a web resource. Some people prefer Google Chrome, someone uses Mozilla Firefox or (less often) Opera, Yandex Browser... And there are also Internet Explorer (Windows), Safari (MAC), and mobile versions of browsers on Android, IOS, and Windows Phone platforms. Therefore, having so many options, it is very important that your site looks the way it was originally intended, under any circumstances.
Thus, the task of the QA team is to check the availability, functionality, site design, as well as fonts and colors, in each browser and on different devices. And believe us, you may be surprised when comparing the display of colors in Windows and MAC OS!
So be smart enough and don&rsquo;t miss this stage.
<h2 dir="ltr" style="text-align: justify;">Testing the visual part</h2>
We&rsquo;d like to start by describing a very important step that must be completed first in the process of layout testing. Its priority is not surprising: we perceive the world with our eyes, so the visual flaws would be discovered almost immediately.
The experienced QA team usually checks:
<ul style="list-style-type: disc;">
<li dir="ltr">
the presence of obvious inconsistencies, visible to the eye: broken blocks, colors inconsistencies, incorrect display of text around images;
</li>
<li dir="ltr">
whether the layout fully corresponds to the implemented project;
</li>
<li dir="ltr">
the grid (vertical/horizontal alignment of fields and blocks);
</li>
<li dir="ltr">
stability of the backgrounds: they should not "float";
</li>
<li dir="ltr">
the page scaling: your page mustn't have visual defects and floated blocks for all reasonable scales (range of 75-150%);
</li>
<li dir="ltr">
the text box resizing (it should not break the layout);
</li>
<li dir="ltr">
the selection of fields of focus, highlighting the fields with errors;
</li>
<li dir="ltr">
the website in different resolutions (1024x600, 1024x768, 1152x864, 1280x800, 1280x1024, 1440x900, 1680x1050, 1920x1080).
</li>
</ul>
<h4 dir="ltr" style="text-align: justify;">In addition, QA experts must ensure that:</h4>
<ul style="list-style-type: disc;">
<li dir="ltr">
all the site elements are being changed in proportion when reducing the window size to less than the minimum technical specifications;
</li>
<li dir="ltr">
every detail looks as intended, nothing is broken;
</li>
<li dir="ltr">
there is no horizontal page scroll at the screen resolutions noticed in the specification;
</li>
<li dir="ltr">
the backgrounds don&rsquo;t drop sharply at higher resolutions.
</li>
</ul>
After completing the checkup of the visual part, QA experts can switch their attention to the site availability testing.
<h2 dir="ltr" style="text-align: justify;">Testing the site availability</h2>
It&rsquo;s the second and equally important phase of the layout test plan, as well as one of the factors helping to assess the quality of the whole site. And assessing the resource's quality is one of the functions of testing, right?
In short, availability is the website&rsquo;s operability. In other words, the QA expert is trying to find out if&hellip;
<ul style="list-style-type: disc;">
<li dir="ltr">
one can select the text in the appropriate blocks;
</li>
<li dir="ltr">
clickable elements (links/buttons) work the way they&rsquo;re intended to;
</li>
<li dir="ltr">
the logo icon is clickable and leads to the main page;
</li>
<li dir="ltr">
the mouse cursor takes the form of a &laquo;<a href="https://www.google.com.ua/search?hl=ru&amp;authuser=0&amp;biw=1093&amp;bih=500&amp;tbm=isch&amp;sa=1&amp;ei=0OjgXanlDo-GwPAP1uO62AY&amp;q=pointer+icon&amp;oq=pointer+&amp;gs_l=img.1.0.0i67l2j0j0i67l5j0l2.1342.1342..3146...0.0..0.104.294.1j2......0....1..gws-wiz-img.e7xHZUmDzlo#imgrc=YyZgaEli-cCy7M:" target="_blank" rel="nofollow noopener">pointer</a>&raquo; or &laquo;<a href="https://www.google.com.ua/search?hl=ru&amp;authuser=0&amp;biw=1093&amp;bih=500&amp;tbm=isch&amp;sa=1&amp;ei=1OjgXZLlJImHwPAPlLG9-AY&amp;q=resize+icon&amp;oq=resize+icon&amp;gs_l=img.3..0i67l2j0i7i30l7j0i8i7i30.98985.98985..99970...0.0..0.111.212.0j2......0....2j1..gws-wiz-img.......0.DsTg3J_Abf8&amp;ved=0ahUKEwiSn9jFkY_mAhWJAxAIHZRYD28Q4dUDCAc&amp;uact=5#imgrc=2hpek_sDtNrKUM:" target="_blank" rel="nofollow noopener">resize</a>&raquo; when hovering over clickable elements and remains &laquo;<a href="https://www.google.com.ua/search?hl=ru&amp;authuser=0&amp;biw=1093&amp;bih=500&amp;tbm=isch&amp;sa=1&amp;ei=VungXafKA4aJrwTynjA&amp;q=default+%D0%BA%D1%83%D1%80%D1%81%D0%BE%D1%80+icon&amp;oq=default+%D0%BA%D1%83%D1%80%D1%81%D0%BE%D1%80+icon&amp;gs_l=img.3...6128.6990..7292...0.0..0.120.926.6j3......0....1..gws-wiz-img.......0i67j0i7i30.HqNo3pW72b8&amp;ved=0ahUKEwinzbWDko_mAhWGxIsKHXIPDAAQ4dUDCAc&amp;uact=5#imgrc=QkUdiGo9K84fPM:" target="_blank" rel="nofollow noopener">default</a>&raquo; when hovering over inaccessible elements;
</li>
<li dir="ltr">
active elements react properly to the mouse cursor (and the unavailable/inactive elements don&rsquo;t react);
</li>
<li dir="ltr">
clickable elements, whose purpose isn&rsquo;t obvious, are provided with tooltips.
</li>
</ul>
<h2 dir="ltr" style="text-align: justify;">Testing the layout reliability</h2>
When describing the required testing set, we mustn&rsquo;t forget about this stage of the process. It&rsquo;s aimed to check the layout reliability, which means the correct site response to adding the real text to the fields. So, the QA team is checking&hellip;
<ul style="list-style-type: disc;">
<li dir="ltr">
the correctness of increasing and decreasing the number of displayed material for information blocks (blocks with descriptions, articles, menus, lists, etc.);
</li>
<li dir="ltr">
the print of the page (if the website suggests such a possibility: say, selling tickets online);
</li>
<li dir="ltr">
readability. If images are switched off, the inscriptions (especially the logo and the main site menu) have to remain readable, and all the information symbols must be signed by the alternative text that a browser displays in cases where it's unable to load the picture (for instance, if the picture was deleted from the server or a visitor has disabled the image display in browser);
</li>
<li dir="ltr">
the input and deletion of data. To check it, one should input a big and small amount of text information into the text fields of forms for filling in.
</li>
<li dir="ltr">
the work of styles. In such a case, one has to observe the site's reaction to inputting the text of different formats (with and without paragraphs, with lists, images, tables, etc). Is everything working as expected?
</li>
</ul>
The reliable layout means the user is at ease during working with a website (specifically, with its textual content) under any condition.
<h2 dir="ltr" style="text-align: justify;">Error 404</h2>
Another step in layout testing is to check broken links, also known as 404 errors.
Let's briefly explain what the number (404) means.
<ul style="list-style-type: disc;">
<li dir="ltr">
The first digit "4" means that there is an error that occurred on the client side. Such an error can be a misspelled URL or a request for a non-existent page. In turn, if the first digit is 5, it would mean an error on the server side.
</li>
<li dir="ltr">
The number "04" identifies the specific error "Not Found" from the 4хх group. Among other mistakes from this group, one might distinguish 400 Bad Request, 401 Unauthorized, 402 Payment Required, 403 Forbidden, and so on.
</li>
</ul>
Try to look at the problem from the user's point of view. When a user encounters a 404 error, the first question coming to his mind is "What should I do next?". Probably, he&rsquo;ll leave the website, unless you find a way to keep him. Obviously, it makes sense to change the standard 404 page which ideally must have the same stylistic structure as the rest of your website.
In general, the custom 404 error page must handle such tasks:
<ul style="list-style-type: disc;">
<li dir="ltr">
the user-friendly design able to keep a user on the website;
</li>
<li dir="ltr">
useful content ready to provide a user with the answer to the question &laquo;What should I do now?&raquo; by giving him simple and clear instructions.
</li>
</ul>
There are many different online services to check 404 errors on your site, one of the most optimal is <a href="https://validator.w3.org/checklink" target="_blank" rel="nofollow noopener">W3C Link Checker</a>.
When moving to this service, you just enter the URL of your web project into the appropriate box, mark suitable options, and click &ldquo;Check&rdquo;. A bit later, the system will give you a full report on your website.
<img src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/pictures/3303/content_content_testingtools3.jpg" alt="multi-level testing" width="800" height="681" />
That's all for now. Good luck with testing!&nbsp;
<div class="blog-banner__wrapper blog-banner__wrapper--large"><a class="blog-banner__link" style="background-image: url('https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/attachments/1166/contact_us_1.jpg');" href="https://agilie.com/contacts" target="_blank" rel="noopener"><img class="image-incut-hide" src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/attachments/1166/contact_us_1.jpg" alt="Effective Layout Testing Tools" width="850" height="300" /></a>
<div class="blog-banner__container">
<div class="blog-banner__title">Feel free to ask any questions. We&rsquo;re always ready to cooperate and help you choose the most effective layout testing tools!</div>
</div>
</div>
&nbsp;
&nbsp;

Web project testing includes a number of different stages. But now we're going to discuss only one of them, namely - the layout testing.

Web projects testing is an extremely important procedure designed to ensure the smooth operation of the site. So it's crucial to choose the most effective layout testing tools ⭐ Not sure where to start? Read our article about multi-level testing and pitfalls you might face during this process ☝

Effective Layout Testing Tools

How can you save your time when developing a rails application? The answer is to use application templates you can build on the basis of simple template our team has recently created. We believe it can be really helpful in your every-day development practice.
<h2 dir="ltr" style="text-align: justify;">What is Rails Application Template?</h2>
Rails Application Template is a basic template for creating Ruby-on-Rails applications. It simplifies the development process when starting a new project and saves your time which can be spent more wisely. Thereby, you can omit all the routine actions and skip to the stages that require you to be more creative and apply your professional skills.
<h2 dir="ltr" style="text-align: justify;">Advantages:</h2>
<ul dir="ltr">
<li style="text-align: justify;">Time-saving. As we've already mentioned, our template saves you from unnecessary work and allows to switch your attention to more interesting tasks.</li>
<li style="text-align: justify;">Easy process of configuring rails gems. You can easily configure our template to fit your needs and add new gems (below, we're describing this process in more details).</li>
<li style="text-align: justify;">Ease of use. This template is really easy-to-use and can be enhanced for your own requirements in a straightforward manner.</li>
</ul>
<h2 dir="ltr" style="text-align: justify;">How to use</h2>
First of all, you should download or clone the template. Then set your ruby version and gemset:
<pre><code class="language-javascript">$ rvm use 2.3.0@myapp --create</code></pre>
When it&rsquo;s done, install rails gem for the gemset:
<pre><code class="language-javascript">$ gem install rails -v 'your_rails_version'</code></pre>
Now you&rsquo;re ready to use our template when creating your application:
<pre><code class="language-javascript">$ rails new myapp -m /path/to/template/bootstrap.rb</code></pre>
That&rsquo;s all! It was quite easy, right? And now you can enjoy your application!
<h2 dir="ltr" style="text-align: justify;">Customization</h2>
The template uses config.yml file for installing and configuring rails gems and other stuff. Below you can find a list of statements able to help you customize your own template.
1) The configuration file consists of several blocks dividing the application generation process into some logic parts.
<pre><code class="language-javascript">rvm: ...
testing: ...
documentation: ...
deploy: ...</code></pre>
2) The main part of each block is gems. So if you want to have more gems in your project just add a new block with a name that corresponds with your appropriate gems block or add your gems to any existing block.
<pre><code class="language-javascript">testing:
&nbsp;&nbsp;gems:
&nbsp;&nbsp;&nbsp;&nbsp;faker: true
&nbsp;&nbsp;&nbsp;&nbsp;rspec-rails:
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;group: test, development
&nbsp;&nbsp;&nbsp;&nbsp;factory_girl_rails:
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;version: ~&gt; 4.8
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;group: test, development</code></pre>
You can use a true value for a gem that in this case will be added to Gemfile as gem 'faker'
You can also pass version and/or group params and they will be used in Gemfile:
<pre><code class="language-javascript">gem 'factory_girl_rails', '~&gt; 4.8', group: [:test, :development]</code></pre>
3) Each block can run its own runner from runners folder if one exists. There you can put any code you want to execute, i.e.
<pre><code class="language-javascript">create_file '.ruby-version', RUBY_VERSION
create_file '.ruby-gemset', app_name
file '.rvmrc', "rvm use #{RUBY_VERSION}@#{app_name}"</code></pre>
4) If you want to perform some actions after gem is added, i.e. run rails generate rspec:install, put callback to the runner and it will be executed when you need. By convention, callback name depends on gem name and should look like:
<pre><code class="language-javascript">"#{your_gem_name.gsub('-', '_')}_callback"</code></pre>
So the full configuration for rspec-rails looks like:
<pre><code class="language-javascript"># config.yml
testing:
&nbsp;gems:
&nbsp;&nbsp;&nbsp;rspec-rails:
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;group: test, development

# runners/testing.rb
def rspec_rails_callback
&nbsp;generate('rspec:install')
end</code></pre>
You can also read our description of this project <a href="https://github.com/agilie/Rails-Application-Template" target="_blank" rel="nofollow noopener">here</a>.
&nbsp;

How can you save your time when developing a rails application? The answer is to use application templates!

Rails Application Template. A basic template for creating Ruby-on-Rails applications

Rails Application Template for Creating Ruby-on-Rails Apps

This is the third part of the article series about our experience of using and adapting the VIPER architecture. In the <a href="https://agilie.com/blog/the-use-and-adaptation-of-the-viper-architecture-on-our-own-example-of-development-part-1">first part</a>, we had discussed the basics of using and adapting the architecture of the VIPER and <a href="https://agilie.com/blog/the-use-and-adaptation-of-the-viper-architecture-on-our-own-example-of-development-part-2">last time</a> we talked about structuring and creating project skeleton for VIPER. It's high time to talk about creating a module in terms of VIPER architecture
Here goes!
Probably, the most time-consuming part of using VIPER architecture is creating lots of additional files and classes. So let&rsquo;s sort it out and first of all see what we should create and why we need it.
<img style="border: none;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631759243.png" alt="" width="512" height="276" />
<h2 dir="ltr" style="text-align: justify;">1. Factory</h2>
The factory is a class responsible for creating a module with parameters (any data needed to be transferred to module we&rsquo;re opening) and completion (a module which opens current one and which has to decide what to do with it). The controller should conform to ModuleInputProtocol.&nbsp;&nbsp;
<pre><code class="language-javascript">&nbsp;func createModule(arguments: NamedValuesType, completion: ModuleCompletionHandler?) -&gt; UIViewController {

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;let storyboard = UIStoryboard(name: storyboardId, bundle: nil)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;let controller = storyboard.instantiateViewController(withIdentifier: initialControllerID)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;let moduleInput = controller as? ModuleInputProtocol

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if let moduleInput = moduleInput {

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;moduleInput.setupInitialState(withArguments: arguments, completion: completion)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;} else {

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;fatalError("\(initialControllerID) moduleInput == nil")

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;return controller

&nbsp;&nbsp;&nbsp;}</code></pre>
It should also define storyboardId and initialControllerID
<pre><code class="language-javascript">&nbsp;&nbsp;&nbsp;// MARK:

&nbsp;&nbsp;&nbsp;let storyboardId = "StartScreen"

&nbsp;&nbsp;&nbsp;let initialControllerID = "StartScreenViewController"</code></pre>
<h2 dir="ltr" style="text-align: justify;">2. Storyboard</h2>
Storyboard is a very important class because all the UI elements should be placed here. Moreover, there&rsquo;re a few requirements for storyboard.
<ul style="list-style-type: disc;">
<li dir="ltr">
Initial storyboard controller should have storyboard id, defined in Factory
</li>
</ul>
<img style="border: none;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631773209.png" alt="" width="512" height="181" />
<ul style="list-style-type: disc;">
<li dir="ltr">
Storyboard has to contain an object with custom class name acting as module initializer (e.g StartScreenModuleInitializer)
</li>
</ul>
<img style="border: none;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631786425.png" alt="" width="512" height="159" />
&nbsp;
<h2 dir="ltr" style="text-align: justify;">3. View</h2>
One of the VIPER module parts is the View which means not only UIView but also all the presentation layers including View, ViewController, DataSources, Delegates, Adapters etc. One more important moment is the interaction between View and other parts of the module, namely the Presenter.
And, of course, we should define input and output protocols. So input protocol (ViewInput) defines methods by which the Presenter calls the View and output protocol (ViewOutput) defines how the View calls the Presenter.
<img style="border: none;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631798746.png" alt="" width="512" height="140" />
<h2 style="text-align: justify;">4. Presenter</h2>
This part acts as a mediator between View and the data layer. It communicates with View in two ways using ViewInput and ViewOutput protocols. And the main task is to process the data retrieved and then assign it to the View.
<h2 style="text-align: justify;">5. Interactor</h2>
The interactor is a class responsible for communication between VIPER module and the external &ldquo;world&rdquo;. In this case, Presenter asks for data by InteractorInput protocol. We don&rsquo;t use InteractorOutput here to transfer data to Presenter for asynchronous operations (e.g API calls) because we usually use PromiseKit for them. We will show how we use it in the final part.
<img style="border: none;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631811810.png" alt="" width="512" height="108" />
<h2 style="text-align: justify;">6. Configurator</h2>
This part of VIPER module is responsible for initial module setup and consists of two parts
<ul style="list-style-type: disc;">
<li dir="ltr">
Initializer (ModuleInitializer).
</li>
</ul>
<pre><code class="language-javascript">class StartScreenModuleInitializer: NSObject {

&nbsp;&nbsp;&nbsp;//Connect with object on storyboard

&nbsp;&nbsp;&nbsp;@IBOutlet weak var startscreenViewController: StartScreenViewController!



&nbsp;&nbsp;&nbsp;override func awakeFromNib() {

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;let configurator = StartScreenModuleConfigurator()

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;configurator.configureModuleForViewInput(viewInput: startscreenViewController)

&nbsp;&nbsp;&nbsp;}

}</code></pre>
StartScreenViewController should be linked to its outlet in storyboard. After loading all UI elements from nib configurator is called to setup all module units (View, Presenter, Interactor).
<ul style="list-style-type: disc;">
<li dir="ltr">
Configurator is the main setup unit.
</li>
</ul>
<pre><code class="language-javascript">class StartScreenModuleConfigurator {



&nbsp;&nbsp;&nbsp;func configureModuleForViewInput&lt;UIViewController&gt;(viewInput: UIViewController) {

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if let viewController = viewInput as? StartScreenViewController {

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;configure(viewController)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}

&nbsp;&nbsp;&nbsp;}



&nbsp;&nbsp;&nbsp;private func configure(_ viewController: StartScreenViewController) {

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;let presenter = StartScreenPresenter()

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;presenter.view = viewController

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;let interactor = StartScreenInteractor()

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;interactor.weatherService = ServicesAssembly.shared.weatherService

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;presenter.interactor = interactor

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;presenter.router = PresentationAssembly.shared.router

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;viewController.output = presenter

&nbsp;&nbsp;&nbsp;}

}</code></pre>
As we can see, it creates Presenter and Interactor, assigning all required services to them and connecting them together. The presenter has a reference to Interactor while View refers to Presenter.
Now module is ready to be shown on the screen.
&nbsp;
It looks clear enough, but in reality, it requires a lot of work to create the same files for each module. And on the other hand, too much time is spent for forming VIPER module, whereas similar screens could be easily created using MVC or MVP. Is it possible to find a solution to this problem? Maybe some script could simplify the whole process by doing all this work for us?
Luckily, there is a great solution, namely - <a href="https://github.com/strongself/Generamba">Generamba</a> (created by Rambler Digital Solutions), which allows defining folder structure, files, and the code they contain. So, by using easy command we receive all these files generated automatically! And the only thing we need to do is to implement business logic to the module. Quite easy, right?
Let&rsquo;s take a look at <a href="https://github.com/strongself/Generamba">Generamba</a> in more details.
<h2 style="text-align: justify;">Generamba in practice</h2>
The first step would be Generamba installation. You can achieve this by using &ldquo;gem install generamba&rdquo; command that requires Ruby 2.2 version.
The next step is to set up Generamba in the project. Run &ldquo;<a href="https://github.com/strongself/Generamba/wiki/Available-Commands">generamba setup</a>&rdquo; command in project root to create <a href="https://github.com/strongself/Generamba/wiki/Rambafile-Structure">Rambafile</a> and add required information about project and author such as author name, company name, target name, etc. It&rsquo;s necessary to properly add new files to the project. And don&rsquo;t worry, this file can be modified any time you want.
Now you should add all the templates you&rsquo;re going to use in the project to the Rambafile. For instance:
<pre><code class="language-javascript">templates:
- {name: rviper_controller}
- {name: local_template_name, local: 'absolute/file/path'}
- {name: remote_template_name, git: 'https://github.com/igrekde/remote_template'}</code></pre>
So you can see three different templates:
<ul dir="ltr">
<li style="text-align: justify;">rviper_controller is a shared template. You can see full list <a href="https://github.com/strongself/generamba-catalog">here</a></li>
<li style="text-align: justify;">local_template_name is template located on your computer locally</li>
<li style="text-align: justify;">remote_template_name is a link to template located on the web</li>
</ul>
Then run &ldquo;<a href="https://github.com/strongself/Generamba/wiki/Available-Commands">generamba template install</a>&rdquo; command to install all templates which will be downloaded and added to &ldquo;Templates&rdquo; folder.
And now it&rsquo;s time for the last step that includes the module generating process. Run &ldquo;<a href="https://github.com/strongself/Generamba/wiki/Available-Commands">generamba gen [Module name] [Template name]</a>&rdquo; to generate all files specified in the template.
<img style="border: none;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631829140.png" alt="" width="512" height="207" />
The script was executed successfully and now we can see what has been created:
<img style="border: none;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631840959.png" alt="" width="512" height="197" />
It's a great result! We used our remote template with name <a href="https://github.com/agilie/swift_viper_template.git">swift_viper_template</a> and got all files generated without any difficulties!
&nbsp;
It's all for now. The final and most interesting part of these series of articles is coming soon. Follow our blog not to miss it!
&nbsp;

This is the third part of the article series about our experience of using and adapting the VIPER architecture.&nbsp;

The use and adaptation of the VIPER architecture

The use and adaptation of the VIPER architecture on our own example of development, part 3

This is the second part of the article about our experience of using and adapting the Viper architecture. In the <a href="https://agilie.com/blog/the-use-and-adaptation-of-the-viper-architecture-on-our-own-example-of-development-part-1" target="_blank" rel="nofollow noopener">first part</a>, we discussed the basics, now it's time to talk about structuring and creating project skeleton for VIPER.
<h2 dir="ltr" style="text-align: justify;">General Info</h2>
To simplify the development process and make it more clear, we usually separate classes into different folders and groups such as Constants, Extensions, Services, Models, Presentation. In addition, Extensions could be divided into smaller groups like UIExtensions, Animations, etc., and Models - into DTO, Business, etc. As for Services, we will discuss them below.
As you can see, there is nothing particularly difficult about these groups, but let's take a closer look at the project structure in terms of VIPER architecture.
<h2 dir="ltr" style="text-align: justify;">1. Services</h2>
For the code clarity, services are better to be divided into several groups like Infrastructure and Business. The first group should contain essential services (API service, Settings service, etc), and the second one consists of all services working with data and business logic.
And there is also the main class called Service Assembly that is a shared instance comprising all services in the app e.g. API service, Settings service, business services, etc.
<pre><code class="language-javascript">protocol ServicesAssemblyProtocol {

&nbsp;&nbsp;&nbsp;var application: UIApplication { get }

&nbsp;&nbsp;&nbsp;var apiService: APIService { get }

&nbsp;&nbsp;&nbsp;var weatherService: WeatherService { get }

}</code></pre>
All services are initialized with the required instances of other ones. For example, UserService might need access to API or Database services.
<pre><code class="language-javascript">class ServicesAssemblyImpl: ServicesAssemblyProtocol {

&nbsp;&nbsp;&nbsp;let application: UIApplication

&nbsp;&nbsp;&nbsp;let apiService: APIService

&nbsp;&nbsp;&nbsp;let weatherService: WeatherService



&nbsp;&nbsp;&nbsp;init(application: UIApplication) {

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;self.application = application

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;apiService = APIServiceImpl()

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;weatherService = WeatherServiceImpl(apiService: apiService)

}

}</code></pre>
All setup logic for services is generally implemented in AppDelegate since we might need it at the very start.
<pre><code class="language-javascript">&nbsp;&nbsp;&nbsp;func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -&gt; Bool {

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;// Setup services

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ServicesAssembly.setup(application: application)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;// Setup everything else if needed

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;return true

}</code></pre>
 <img style="border: none;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631576231.png" alt="" width="512" height="483" />
<h2 dir="ltr" style="text-align: justify;">2. Presentation</h2>
Presentation&nbsp;is a group with all layout logic inside. Let&rsquo;s examine its structure in depth.
PresentationAssembly is a shared class containing references to the presentation layer.
<pre><code class="language-javascript">protocol PresentationAssemblyProtocol {

&nbsp;&nbsp;&nbsp;var router: AppRouterProtocol! { get }

&nbsp;&nbsp;&nbsp;var whisper: InAppNotificationsProvider! { get }

}



class PresentationAssembly: PresentationAssemblyProtocol {

&nbsp;&nbsp;&nbsp;static let shared = PresentationAssembly()

&nbsp;&nbsp;&nbsp;var router: AppRouterProtocol!

&nbsp;&nbsp;&nbsp;var whisper: InAppNotificationsProvider!

&nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;func setup(withNavigation navigation: UINavigationController, modules: Array&lt;ModuleFactoryProtocol&gt;, urlScheme: String, services: ServicesAssemblyProtocol) {

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;router = AppRouterImpl(withNavigation: navigation, modules: modules, urlScheme: urlScheme)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;whisper = InAppNotificationsProviderImpl(withNavigation: navigation)

}

}</code></pre>
&nbsp;
<img style="border: none;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631589098.png" alt="" width="512" height="278" />
Let&rsquo;s consider Application root more carefully.
<h2 dir="ltr" style="text-align: justify;">Application root</h2>
Application root is an entry point to the app. It is called by AppDelegate and responsible for launching an application and all configuration needed before that moment.&nbsp;
<pre><code class="language-javascript">&nbsp;&nbsp;func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -&gt; Bool {

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;// Setup here &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;// Start application

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;appRoot = ApplicationRoot(withNavigation: navigationController)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;appRoot.start()

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;return true

}</code></pre>
It sets up every necessary service, router, presentation stuff and chooses a module to show first (log in or main screen, for instance). Application root also contains all existing modules inside in order to know about each of them to be able to create it.
<img style="border: none;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631600777.png" alt="" width="512" height="177" />
<pre><code class="language-javascript">class ApplicationRoot: NSObject {

&nbsp;&nbsp;&nbsp;let modules : Array&lt;ModuleFactoryProtocol&gt; = [

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;StartScreenFactory.shared,

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DetailsScreenFactory.shared

&nbsp;&nbsp;&nbsp;]



&nbsp;&nbsp;&nbsp;// MARK:

&nbsp;&nbsp;&nbsp;fileprivate let router: AppRouterProtocol

&nbsp;&nbsp;&nbsp;fileprivate let whisper: InAppNotificationsProvider



&nbsp;&nbsp;&nbsp;init(withNavigation navigation: UINavigationController) {

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;let services = &nbsp;ServicesAssembly.shared

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;let presentation = PresentationAssembly.shared

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;presentation.setup(withNavigation: navigation, modules: modules, urlScheme: "viper", services: services)

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;router = presentation.router

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;whisper = presentation.whisper &nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;super.init()

}



&nbsp;&nbsp;&nbsp;func start() {

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;let urn = StartScreenFactory.shared.moduleURN

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;router.pushModule(byUrn: urn, animated: true, completion: { (_) in

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;//completion

})

}

}</code></pre>
<h2 dir="ltr" style="text-align: justify;">Application router</h2>
AppRouter contains all routing logic. It is created by Application root and responsible for navigation between modules e.g. push/pop or present/dismiss etc.
<pre><code class="language-javascript">protocol AppRouterProtocol {

&nbsp;&nbsp;&nbsp;var navigationController: UINavigationController { get }

&nbsp;&nbsp;&nbsp;func pushModule(byUrn urn: String, animated: Bool, completion: ModuleCompletionHandler?) &nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;func presentModule(byUrn urn: String, animated: Bool, completion: ModuleCompletionHandler?) &nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;func popToViewController(_ controller: UIViewController, animated: Bool)

&nbsp;&nbsp;&nbsp;func dismissCurrentController(animated: Bool)

}</code></pre>
It&rsquo;s global in general but can be moved to each module or added to some of them depending on the complexity if we want so.
<img style="border: none;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631615470.png" alt="" width="512" height="314" />
As you can see Routing group also contains ModuleFactoryProtocol
<pre><code class="language-javascript">protocol ModuleFactoryProtocol {

&nbsp;&nbsp;&nbsp;/**

&nbsp;&nbsp;&nbsp;&nbsp;* Module URN ( ex. profile:{userID} )

&nbsp;&nbsp;&nbsp;&nbsp;*/

&nbsp;&nbsp;&nbsp;var moduleURN: String { get } &nbsp;&nbsp;&nbsp;

&nbsp;&nbsp;&nbsp;/**

&nbsp;&nbsp;&nbsp;&nbsp;* Create module with arguments

&nbsp;&nbsp;&nbsp;&nbsp;* Returns module root UIViewController, must implement ModuleInputProtocol.

&nbsp;&nbsp;&nbsp;&nbsp;*/

&nbsp;&nbsp;&nbsp;func createModule(arguments: NamedValuesType, completion: ModuleCompletionHandler?) -&gt; UIViewController

}</code></pre>
which defines the way how new module can be created and ModuleInputProtocol
<pre><code class="language-javascript">protocol ModuleInputProtocol {

&nbsp;&nbsp;&nbsp;&nbsp;/**

&nbsp;&nbsp;&nbsp;&nbsp;* Configure module with arguments.

&nbsp;&nbsp;&nbsp;&nbsp;* Calls form Module factory

&nbsp;&nbsp;&nbsp;&nbsp;*/

&nbsp;&nbsp;&nbsp;func setupInitialState(withArguments args: NamedValuesType, completion: ModuleCompletionHandler?)

}</code></pre>
defines the way module could be configured with additional parameters.
Presentation group also contains any additional groups required by the app. For example, InAppNotifications (alerts, toast etc), StyleKit (responsible for styling application if necessary), SocialServices (Facebook, Twitter, etc), and lots of other logic your app may need.
<h2 dir="ltr" style="text-align: justify;">Views</h2>
Views is created for keeping all the custom layouts which are placed just here. Besides, it can include the following groups inside such as Layouts, Cells, Collections, etc.
<h2 dir="ltr" style="text-align: justify;">User stories</h2>
This part consists of all your screens and UI logic and contains every VIPER module that is located here and should include: Factory, Configurator, View, Presenter, and Interactor. 
We will describe the module structure in the next article and right now just say that it may have storyboard or xib file inside if needed.
<img style="border: none;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631628252.png" alt="" width="504" height="512" />
So, to conclude, to simplify finding the specific class or service let&rsquo;s mention that the structure of the project is extremely clear. In addition, it&rsquo;s good practice to keep the group and folder structure the same way. 
In the next - third - part of our article we'll tell you about creating a module in terms of VIPER architecture: units, their responsibilities, etc.
Read our blog to know more!
&nbsp;

This is the second part of the article about our experience of using and adapting the Viper architecture.&nbsp;

Structuring and creating project skeleton for VIPER architecture

The use and adaptation of the VIPER architecture on our own example of development, part 2

In this article, we want to share with you our experience of using and adapting the architecture of the Viper by describing our own example of development. And today we're going to discuss the basics&hellip; &nbsp;
Many developers face an issue when code becomes hard to read, debug and fix bugs. Classes become huge together with adding features and development turns to infinite &ldquo;bugfixing&rdquo;. That&rsquo;s why it&rsquo;s important to choose proper software architecture before developing an application, otherwise, it will consume much time to maintain and improve. As a result, it will help to save time and efforts, so proper architecture is the first step to success!
<h2 style="text-align: justify;">Perfect architecture</h2>
Quality architecture should meet the following requirements:
<ol dir="ltr">
<li style="text-align: justify;">The effectiveness of performing the assigned tasks. If designed architecture performs the tasks poorly and doesn't fit into the requirements of functionality, stability, performance, and development time, it can hardly be called a good one.</li>
<li style="text-align: justify;">Well readable and understandable code. First and foremost, a code should be clear and properly structured.</li>
<li style="text-align: justify;">The scalability and flexibility of the system. A good architecture allows you to painlessly add new entities and functions, as well as make changes to existing functionality.</li>
</ol>
However, there is no reason to reinvent the wheel and spend a lot of time developing a completely unique architectural pattern. It's much easier to use the existing one.
There&rsquo;re several most famous architectures named MVC, MVP, MVVM, VIPER. Let&rsquo;s probe deep into each of them.
<h2 dir="ltr" style="text-align: justify;">MVC (Model View Controller)</h2>
MVC is the most simple architecture Apple recommends.
<img style="border: none; width: 512px; height: 208px;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631376053.png" alt="^56BDEBB44AF88BAB8B39A1A9F8FC649A23FC487FB5D45024D5^pimgpsh_fullsize_distr.png" />
The basic idea of MVC architecture is to split up all the elements (fragments) of the code into three separate units: the Model (domain data or a data access layer), the View (user interface) and the Controller (interface between Model and View). MVC allows each block to be controlled independently of the two others, and it greatly simplifies and systematizes the development process.
MVC implies that the Model manipulates data and provides it to the Controller that renders the View. And the View remains stateless just displaying data of the Model to a user.
However, the described model may not work perfectly in all conditions. And in reality, the View and the Controller often become a single unit looking like this:
<img style="border: none; width: 512px; height: 61px;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631386327.png" alt="2.png" />
So, ViewController transforms into the Massive View Controller forced to handle almost all the processes itself. And the main task for developers, in this case, is to offload it.
<div>
<h2 dir="ltr" style="text-align: justify;">MVP (Model View Presenter)</h2>
It turned out that in some cases MVC architecture is not working as effectively as one expects (for the reasons described above). So there was MVP pattern designed, having become a bit improved version of MVC. 
The difference between MVC and MVP is the Presenter acting as the mediator between the View (actually ViewController) and the Model. The Presenter significantly unloads the ViewController by moving business logic to the Presenter, so the ViewController is only responsible for the layout and its lifecycle.
<img style="border: none; width: 512px; height: 199px;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631396862.png" alt="" />
This architecture makes it easier to mock the View, the Presenter and the Model that leads to better testability of the code which is an obvious advantage of MVP.
<h2 dir="ltr" style="text-align: justify;">MVVM (Model View ViewModel) </h2>
Another popular pattern is MVVM (Model View ViewModel). It looks similar to MVP architecture, but instead Presenter it has ViewModel between the View (view controller) and the Model (data).
<img style="border: none; width: 512px; height: 43px;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631408723.png" alt="3r.png" />
The important difference of this model from the MVP is that ViewModel doesn&rsquo;t refer to View, it works directly with model updating it with user interactions from View and receives updates from Model updating only itself (not View). View can receive updates using observer if needed. So ViewModel prepares the data for View that unloads controller.
<div>
<h2 dir="ltr" style="text-align: justify;">VIPER</h2>
The last architecture we will talk about is VIPER. It&rsquo;s a very effective architecture pattern, in fact, the first one that cares about navigation (routing) between modules.
It consists of 5 parts: View, Presenter, Interactor, Entity, Router.
<ul dir="ltr">
<li style="text-align: justify;">The view is the ViewController. The View&rsquo;s waiting for the Presenter to transmit the content and display it to a user; it never requests the data from the Presenter.</li>
<li style="text-align: justify;">Presenter prepares data for the View. It gathers data from user interactions and can send requests to the Interactor. The Presenter also gets results from the Interactor and convert the results to a state being most effective to display on the View.</li>
<li style="text-align: justify;">Interactor (a new unit) contains the business logic and networking for managing objects (Entity) to perform a specific task.</li>
<li style="text-align: justify;">Entity is the objects managed by the Interactor. So it&rsquo;s actually a model.</li>
<li style="text-align: justify;">Router (another new unit) is responsible for segues between modules.</li>
<li style="text-align: justify;">Data Store (e.g., web service, database) provides the Entity to the Interactor. Applying its business logic, Interactor selects the Entity from the data store, manages it and then returns it in an updated form back to the datastore.</li>
</ul>
<img style="border: none; width: 512px; height: 196px;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631418693.png" alt="4.png" />
VIPER module is a user story that can be represented either as one screen or as a whole story. The good example is a registration flow consisting of several screens such as SignUp, Confirmation, etc.
Each module being an independent part requires an additional unit able to manage the entire process. This role is played by the Configurator which task is not only to create a module but also provide it with all necessary Services and information.
<h2 dir="ltr" style="text-align: justify;">Improving and Simplifying VIPER at the same time</h2>
VIPER architecture was reliable and usable from the outset, but <a href="https://github.com/strongself/The-Book-of-VIPER" target="_blank" rel="nofollow noopener">Rambler Digital Solutions</a> has improved and simplified it even more. Let&rsquo;s take a look at the main changes:
<ol dir="ltr">
<li style="text-align: justify;">Assembly functions which Wireframe was responsible for are moved to Configurator now. So, after this modification, Wireframe is in charge of Routing and nothing else.</li>
<li style="text-align: justify;">The router has become global</li>
<li style="text-align: justify;">All data transfer is executed according to ModuleInput and ModuleOutput protocols</li>
<li style="text-align: justify;">View is not only ViewController now; it acts as a presentation layer containing several parts (View, DataSource&rsquo;s. Delegate&rsquo;s, etc.)</li>
<li style="text-align: justify;">A new service layer has been added to a module with dependency injection into interactor. Thanks to this improvement a module interacts just with required services (they make networking, storing, collecting, etc.).</li>
</ol>
Thus, the VIPER is quite a useful architectural system, allowing to distinguish all of the logic, so that every class performs only actions it is responsible for.
<img style="border: none; width: 512px; height: 240px;" src="https://d12zh9bqbty5wp.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1676631429726.png" alt="6.png" />
This is the first part of our article about using and adapting the Viper architecture. In the <a href="https://agilie.com/blog/the-use-and-adaptation-of-the-viper-architecture-on-our-own-example-of-development-part-2" target="_blank" rel="nofollow noopener">second part</a>, we're going to discuss structuring and creating project skeleton for VIPER.
Follow our blog to learn more about the architecture of VIPER!
</div>
</div>

In this article, we want to share with you our experience of using and adapting the architecture of the Viper.&nbsp;&nbsp;

General info about software architectures

The use and adaptation of the VIPER architecture on our own example of development, part 1

- Media content features for software distribution companies;&nbsp; 
- Processes automatization for production teams;&nbsp; 
- Reach an audience and work on retention of users;&nbsp; 
- Different channels to talk to the audience;&nbsp; 
- Improve a visibility for startups;

<iframe allowfullscreen="" frameborder="0" height="485" marginheight="0" marginwidth="0" scrolling="no" src="//www.slideshare.net/slideshow/embed_code/key/3r5YcQzXyOaVch" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" width="595"></iframe>

<div style="margin-bottom:5px"><a href="//www.slideshare.net/agilie/b2b-media-content-broadcast-and-live-streaming" target="_blank" title="B2B media content broadcast and live streaming">B2B media content broadcast and live streaming</a> from <a href="//www.slideshare.net/agilie" target="_blank">Agilie Team</a></div>

Read about Media content features for software distribution companies and&nbsp;Processes automatization for production teams.

Media content, audience, visibility for startups;

B2B media content broadcast and live streaming

Read our detailed case study on how we&nbsp;tried out different video libraries for the Android version of our live video streaming app b.live.

Our detailed case study on how we tried out different video libraries for the Android version of our live video streaming app b.live, and what affected our final decision.

How We Integrated a Video Library Into Our Live Video Streaming App

Apple&rsquo;s App Transport Security (or simply ATS) is a networking security feature that forces an app to use an HTTPS web services connection instead of an HTTP. Apple added ATS as an optional feature with the introduction of iOS9 in 2015: developers were still allowed to switch it off. However, at WWDC 2016 Apple <a href="https://techcrunch.com/2016/06/14/apple-will-require-https-connections-for-ios-apps-by-the-end-of-2016/">announced</a> that starting from 2017 the feature will be mandatory for all apps submitted to App Store.
In this article, we are going to speak a little more about the App Transportation Security feature, its role in&nbsp;<a href="https://agilie.com/expertise/technology/mobile-development">iOS app development</a>, and learn how to add Domain Exceptions considering the new ATS requirements.
<h3>A bit more about ATS and its requirements</h3>
App Transport Security is basically a set of rules that ensure iOS, macOS, watchOS, and tvOS apps and app extensions connect to web services they work with using secure connection protocols. This improves users&rsquo; privacy and integrity of their data and safeguards it from various malicious parties.
By configuring the NSAppTransportSecurity key&rsquo;s value in your app&rsquo;s Info.plist file, <a href="https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html">you can configure</a> your network connections&rsquo; security in a different of ways.&nbsp;
You can:
<ul>
<li>add exceptions for insecure communication with particular servers;</li>
<li>disable ATS protection for web views or media, while still using the feature to protect other data in your app;</li>
<li>enable Certificate Transparency and other new security features.&nbsp;</li>
</ul>
Currently, ATS requires your app to connect to servers that:
<ul>
<li>support the Transport Layer Security (TLS) protocol version 1.2 or later;</li>
<li>use AES-128 encryption standard and SHA-2-signed certificates;</li>
<li>provide Forward Secrecy protocols.</li>
</ul>
However, since Forward Secrecy protocols aren&rsquo;t used by the majority of servers yet, Apple can accept this as a reasonable justification for including ATS in your app even if the servers it connects with doesn't provide Forward Secrecy.
Among other reasons that can justify including ATS in your app without meeting all requirements are:
<ul>
<li>the server is not fully ATS compatible;</li>
<li>you use a third-party service or SDK that does not support ATS at the moment;</li>
<li>you don&rsquo;t have the time or the resources to add the required functionality yet.</li>
</ul>
However, these exceptions are temporary: Apple just gives developers some time to get ready to use ATS as a mandatory with future updates. And the first requirements update is coming real soon.
<h3>The new requirements&nbsp;</h3>
Since January 1, 2017, the ATS feature will be mandatory for all apps on App Store and for the servers they connect with. If you don&rsquo;t want your app to be rejected from App Store, you must turn on and configure ATS according to the new requirements.
Here are three cases when an exempted ATS will lead to an app rejection from app store:
<ul>
<li>NSAllowsArbitraryLoads, which disables ATS for all domains. ATS can be re-enabled for specific domains by using an exception domain dictionary.</li>
<li>NSExceptionAllowsInsecureHTTPLoads, which disables ATS for a single domain, to allow insecure HTTP loads to that domain.</li>
<li>NSExceptionMinimumTLSVersion, which enables support for TLS versions that are older than 1.2 for a specific domain.</li>
</ul>
Other ATS exemptions such as, for example, NSExceptionRequiresForwardSecrecy can be enabled and won&rsquo;t trigger an App Store rejection.
However, the three blacklisted exemptions mentioned above can lead to rejection only in case the servers an app connects to are under the developer&rsquo;s control. For third-party servers, on the other hand, all ATS exemptions can be used: according to Apple, using a server you don&rsquo;t have control over is a reasonable excuse for developers to use the exemptions.
To do this, you will need to identify all third-party servers your app connects to and to add the ATS exemptions specific to the domains.
<h3>Why Apple now enforces ATS</h3>
Unlike web browsers that designate the type (HTTP or HTTPS) of connection they use, mobile apps don&rsquo;t let users know whether they use regular or secure web connection.&nbsp;
The initial implementation of ATS as an optional feature was surely only the first step towards increasing mobile app&rsquo;s security. Now as app developers got to know the new networking security feature, Apple takes one more step closer to ensuring secure web connection within their products.
<h3>How to add&nbsp;Domain Exceptions</h3>
Here&rsquo;s what you do to add a third-party domain as an exception for your ATS.
Add the NSExceptionDomains key to the NSAppTransportSecurity dictionary of your app&rsquo;s Info.plist&nbsp;file. The key&rsquo;s value is a dictionary which contains keys describing domain exceptions:
<pre><code class="language-xml">&lt;key&gt;NSAppTransportSecurity&lt;/key&gt;
&lt;dict&gt;
&nbsp; &lt;key&gt;NSAllowsArbitraryLoads&lt;/key&gt;
&nbsp; &lt;false/&gt;
&nbsp; &lt;key&gt;NSExceptionDomains&lt;/key&gt;
&nbsp; &lt;dict&gt;
&nbsp; &nbsp; &lt;key&gt;agilie.com&lt;/key&gt;
&nbsp; &nbsp; &lt;dict&gt;
&nbsp; &nbsp; &nbsp; &lt;key&gt;NSIncludesSubdomains&lt;/key&gt;
&nbsp; &nbsp; &nbsp; &lt;true/&gt;
&nbsp; &nbsp; &nbsp; &lt;key&gt;NSExceptionAllowsInsecureHTTPLoads&lt;/key&gt;
&nbsp; &nbsp; &nbsp; &lt;true/&gt;
&nbsp; &nbsp; &lt;/dict&gt;
&nbsp; &lt;/dict&gt;
&lt;/dict&gt;</code></pre>
Here, we enable ATS and set a domain exception for agilie.com. The NSIncludesSubdomains key means we include all subdomains of this domain as exceptions, too. The NSExceptionAllowsInsecureHTTPLoads key allows the non-HTTPS requests for the domain and its subdomains. &nbsp;
Setting the value of the NSAllowsArbitraryLoads key to true applies the ATS rules to the domain and subdomains, while they will remain exceptions.
You can also add multiple domain exceptions at a time and apply the exceptions not only to the HTTPS protocol network requests but also to the configuration of the server your app connects to.
Here&rsquo;s an example:
<pre><code class="language-xml">&lt;key&gt;NSAppTransportSecurity&lt;/key&gt;
&lt;dict&gt;
&nbsp; &lt;key&gt;NSAllowsArbitraryLoads&lt;/key&gt;
&nbsp; &lt;false/&gt;
&nbsp; &lt;key&gt;NSExceptionDomains&lt;/key&gt;
&nbsp; &lt;dict&gt;
&nbsp; &nbsp; &lt;key&gt;anotherdomain.com&lt;/key&gt;
&nbsp; &nbsp; &lt;dict&gt;
&nbsp; &nbsp; &nbsp; &lt;key&gt;NSIncludesSubdomains&lt;/key&gt;
&nbsp; &nbsp; &nbsp; &lt;true/&gt;
&nbsp; &nbsp; &nbsp; &lt;key&gt;NSExceptionMinimumTLSVersion&lt;/key&gt;
&nbsp; &nbsp; &nbsp; &lt;string&gt;TLSv1.0&lt;/string&gt;
&nbsp; &nbsp; &lt;/dict&gt;
&nbsp; &nbsp; &lt;key&gt;onemoredomain.com&lt;/key&gt;
&nbsp; &nbsp; &lt;dict&gt;
&nbsp; &nbsp; &nbsp; &lt;key&gt;NSExceptionRequiresForwardSecrecy&lt;/key&gt;
&nbsp; &nbsp; &nbsp; &lt;false/&gt;
&nbsp; &nbsp; &lt;/dict&gt;
&nbsp; &nbsp; &lt;key&gt;agilie.com&lt;/key&gt;
&nbsp; &nbsp; &lt;dict&gt;
&nbsp; &nbsp; &nbsp; &lt;key&gt;NSIncludesSubdomains&lt;/key&gt;
&nbsp; &nbsp; &nbsp; &lt;true/&gt;
&nbsp; &nbsp; &nbsp; &lt;key&gt;NSExceptionAllowsInsecureHTTPLoads&lt;/key&gt;
&nbsp; &nbsp; &nbsp; &lt;true/&gt;
&nbsp; &nbsp; &lt;/dict&gt;
&nbsp; &lt;/dict&gt;
&lt;/dict&gt;</code></pre>
Now you know how to add domain exceptions. But will it be possible with the further ATS updates? Let&rsquo;s sum up what we know to expect so far.
<h3>The future of ATS</h3>
While the NSExceptionRequiresForwardSecrecy key won&rsquo;t lead to app rejection from App Store, this will probably change with the future ATS requirements updates. This is likely to happen as soon as more servers will provide the Forward Secrecy protocols.
Some hints were given during Apple&rsquo;s <a href="https://developer.apple.com/videos/wwdc2016">What&rsquo;s New in Security</a> presentation at WWDC 2016. Here&rsquo;s what you as an iOS developer should take into account next year:
<ul>
<li>The SHA-1-signed certificates won&rsquo;t be used since <a href="https://www.bleepingcomputer.com/news/security/google-to-show-errors-for-sha1-certificates-starting-with-chrome-56/">they are to be blocked</a> by Google.</li>
<li>The 3DES TLS cipher suites are better&nbsp;to be disabled since they&rsquo;re only needed for the compatibility with the obsolete Windows XP.</li>
<li>You should start deploying the Certificate Transparency and OCSP Stapling (aka TLS Certificate Status Request) technologies to your app servers.</li>
</ul>
Luckily, Apple understands that it&rsquo;s impossible to cut all insecure connections at a time, and they are ready to make exceptions for those who can&rsquo;t meet all the requirements.
But don&rsquo;t rely on these exceptions heavily - their main purpose is to get you ready to use ATS as a mandatory feature in the nearest future. Apple wants you to provide greater security to your app and to people who use it, so complying with the new ATS requirements will help you build trust with your users and - ultimately - provide better services.

In this article, we'll speak&nbsp;about Apple's App Transportation Security feature and highlight its importance for mobile app development.

Apple's App Transportation Security feature, its importance for mobile app development, and learn how to add Domain Exceptions considering the new ATS requirements that will be introduced in 2017.

How to Add Domain Exceptions to Comply with Apple's New ATS Requirements 

With the release of the new Apple TV running on tvOS users get a chance to play games, use applications, watch movies and share their experiences. All these new capacities also bring new possibilities to app developers.

<div>
<img alt="Apple TV running on tvOS" height="369" src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/pictures/4205/content_content_content_content_apple-tv_1.jpg" width="800" />

&nbsp;

&nbsp;

&nbsp;
</div>

New Apple TV uses the latest iOS frameworks and unique tvOS&nbsp;ones. During developing an app the one will notice that the similarity with iOS combined with support for multiuser experience, opens up new ways and possibilities for app development, that are not found on iOS devices. It is possible to make new apps or update existing iOS applications using Objective-C or Swift. On the official Apple website the unique possibilities of Apple TV are described and the detailed information is available for the developers, so they have a chance to check it before starting a new app for tvOS.

It is worth saying that developing an app&nbsp;for Apple TV is very similar to creating an application for iOS. It is possible to create games, utilities, media-applications and others using the same techniques and frameworks as for iOS. New and existing applications may be used both on iOS and new Apple TV, enabling the multiuser experience.

<img alt=" app for Apple TV" height="444" src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/pictures/4206/content_content_apple-tv-2.jpeg" width="592" />

Apple TV does not have a mouse to interact with an app, but there is a better way to do that &ndash; it is a Siri Remote or a game controller for a user&#39;s choice, which enables them to move around the screen. In general, with the new Apple TV user&#39;s experience will be totally different. Mac and iOS devices are generally used as single-user experience. It is different with the new Apple TV, as it can easily interact with several people at the same time. They can be sitting in a room and interact with Apple TV as well as with each other.

After the deeper study on Apple TV possibilities and its new tvOS our team has got several ideas of tvOS apps. In order to know more about it, please check our Services page on our website.

Subscribe to our blog and please follow us on:

<div style="line-height: 20.8px;">
<div style="line-height: 20.8px;">Facebook:&nbsp;<a href="https://www.facebook.com/pages/Agilie/282259051924123" rel="nofollow">https://www.facebook.com/pages/Agilie/</a></div>

<div style="line-height: 20.8px;">Twitter:&nbsp;<a href="https://twitter.com/agile_ninjas" rel="nofollow" style="line-height: 20.8px;">https://twitter.com/agile_ninjas</a></div>
</div>

If you have any questions or would like to contact us about possible request on design or mobile friendly websites/mobile apps development please use&nbsp;<a href="/contacts">Contact form</a>.

New&nbsp;Apple TV&nbsp;uses the latest iOS frameworks and unique&nbsp;tvOS&nbsp;ones.

With the release of the new Apple TV running on tvOS users get a chance to play games, use applications, watch movies and share their experiences.

The New Apple TV

During the last Apple presentation there were a lot of talks about a&nbsp;new Handoff feature. Its main purpose is to share information between different Apple devices using the same Apple ID. For example, starting to work on the iPad&nbsp;user might switch it to the Mac and continue doing the same task&nbsp;on another device.
<div>This release of Handoff works with the most important Apple&rsquo;s applications.</div>
<div>- Safari opens the page you&rsquo;ve just read;</div>
<div>- Apple Maps could display the same address and you don&rsquo;t need to take care of the map scale. The application will do this itself;</div>
<div>- Calendar could open the agenda by the date you&nbsp;looked for;</div>
<div>- Pages, Numbers, Keynote allow editing from the same place on the document;</div>
<div>- Mail allows to continue writing your emails;</div>
<div>- Messages do the trick for lazy typing. It opens the draft message on another device;</div>
<div>- Reminders open&nbsp;the same list and Contacts application displays the same contact.</div>
<div>&nbsp;</div>
There are a few technical requirements to use Handoff on your devices. Your computer must be running by OS X Yosemite, iPad, iPhone or iPod Touch should use iOS 8. Your devices should be listed in the same iCloud account and support Bluetooth 4.0 LE.
iOS developers might be interested to use Handoff features on their own applications. Handoff is based on the concept of User Activity. User Activity is independent piece of information and it can be freely transferred. Apple&rsquo;s NSUserActivity class is the implementation of this concept, it represents the state of the application.
There are a few main components of NSUserActivity:
- ActivityType is an unique string identifier represented by Reverse DNS notation. For Example, <code>&laquo;com.agilie.exampleapp.addFriends&raquo;</code> All activity types should be included in Info.plist configuration file.
- UserInfo is the dictionary to store application data. By this information the application will restore the state on another device. For example, we might store information about user friends. <code>@ {" exampleapp.participants.key": @ [ &laquo;John Smith&rdquo;, &laquo;Bill Jones", &laquo;Andy Robson"]}</code> UserInfo allows us to store native data types like NSArray, NSData, NSDate, NSDictionary, NSNull, NSNumber, NSSet, NSString, NSUUID, and NSURL.
Mobile application developers could implement a few methods to start use these components. Current UIViewController should start the activity by invocation of <code>becomeCurrent()</code> method. To get periodically updates this UIViewController should overwrite the method <code>updateUserActivityState (activity :)</code>
The target device needs to handle the start by AppDelegate&rsquo;s methods <code>application: willContinueUserActivityWithType:</code> and <code>application: continueUserActivity: restorationHandler:</code> The first method tells the application about user activity by some type and starts to load the data. The second method is called when the data from UserInfo is loaded and we can restore the state of the application.
As you can see Handoff implementation is quite simple and transparent. Our future experience in&nbsp;mobile apps developing will show if Handoff provides to the users the benefits or will remain as another cool but unpopular innovation from Apple.

During the last Apple presentation there were a lot of talks about a&nbsp;new Handoff feature. Its main purpose is to share information between different Apple devices using the same Apple ID. For example, starting to work on the iPad&nbsp;user might switch it to the Mac and continue doing the same task&nbsp;on another device.

Technical introduction to Apple’s HandOff by Agilie

Technical Introduction to Apple’s HandOff

According to the last survey smartphone users prefer to use mobile apps instead of website&nbsp;mobile versions. Among 3.5 thousand of respondents from different corners of the world who participated in the survey 85% say that they consider&nbsp;mobile apps to be much more convenient and quicker than mobile versions of sites.

Mobile apps&nbsp;simplify our lives &ndash; we can make purchases, order food from a restaurant, read news, check weather. They are used as business diary, organizer, help us to carry on personal diary,&nbsp;take care of our health, read books, etc. Today&nbsp;mobile applications&nbsp;help people to make bank transactions, pay for goods, bills, book seats and tickets. Thus, users prefer to use&nbsp;mobile applications for iOS and Android&nbsp;to communicate with the companies.

Of course, mobile websites have certain advantages. First of all, the development of mobile site&nbsp;is cheaper. Moreover, in some cases it&rsquo;s easier to maintain them, they don&rsquo;t need installation and it&rsquo;s easier to promote them on the Internet. However, mobile apps are more preferable than mobile sites to increase customers&rsquo; loyalty, as they are easier to use: no need to enter the site address every time, and the application runs faster than the site. Also you have an opportunity to use the functionality of device (camera, GPS).

Some experts believe that an application is more convenient only if the client uses it constantly. A mobile app for iOS and Android is more convenient when it is already installed. Mobile site is run by those users who need an urgent access to information. At the same time mobile apps should be applied for the fullest functionality.

So mobile applications have some significant advantages. The main are the adaptation for mobile devices, more extensive functionality and high level of usability.

To be the leader of the market you should focus on the target audience and consumer. In such case, your own mobile app for clients&rsquo; service will give you an essential advantage among your rivals. Appeal to the professionals and you will receive really quality and useful product!

Sincerely, Agilie team.

&nbsp;

Mobile apps simplify our lives &ndash; we can make purchases, order food from a restaurant, read news, check weather. They are used as business diary, organizer, help us to carry on personal diary,&nbsp;take care of our health, read books, etc.&nbsp;They are used as business diary, organizer, help us to carry on personal diary, etc.&nbsp;Thus, users prefer to use mobile applications for iOS and Android to communicate with the companies.

Mobile applications help people to make bank transactions, pay for goods, bills, book seats and tickets. Thus, users prefer to use mobile applications for iOS and Android to communicate with the companies.

Mobile Apps Become More Popular

<img alt="Insurance Apps and Website Design" height="340" src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/pictures/4194/content_content_insurance_pic1.jpg" width="340" />Mobile technologies greatly influence our life. Mobile app is a good tool to manage health with tasks, reminders, alerts etc. Moreover, mobile apps not only take care of your health, but help you in troublesome situations. A lot of insurance companies develop special insurance apps which make cooperation with customers more convenient and innovative. Modern and intuitive application allows users to use the services of insurance online, as well as to receive information about the company&#39;s services, promotions and locations.

For insurance companies development of mobile apps &amp; insurance website design is a good opportunity to increase the loyalty of existing customers and to attract new clients. In this article we want to emphasize the main facilities of mobile insurance apps.

<ul>
	<li>
	Payments
	</li>
</ul>

An access to policies for users and ability to make payments online.

<ul>
	<li>
	Various insurance policies
	</li>
</ul>

Browsing various insurance policies after answering a series of questions to find out user&rsquo;s preferences.

<ul>
	<li>
	Proof of insurance
	</li>
</ul>

Proof of insurance right from user&rsquo;s smartphone to simplify customer interaction.

<ul>
	<li>
	Reminders
	</li>
</ul>

Sending reminders about policy renewals and provision of clear guidance for customers.

<ul>
	<li>
	Claims
	</li>
</ul>

Report of claims through the app.

<ul>
	<li>
	Accident Help
	</li>
</ul>

Connection with emergency services from the place of an accident.

<ul>
	<li>
	Contacts
	</li>
</ul>

Searching for the nearest office or service center.

The potential of IT insurance and mobile application market is really huge. In some years each company will be obliged to have a quality mobile application not to become the market outsiders. Today requirements for mobile apps for IOS and Android become more and more high. In other words, the application should be not only comfortable and functional, but also bring esthetic pleasure to user. Icons of mobile apps that the user sees on the screen of the device are the face of your company.

By implementing mobile technologies for your mobile insurance company you will achieve two goals at once. Firstly, you receive effective tool that in many cases will replace customer&rsquo;s personal visit to the office, thus will save his time and effort. Secondly, you get one more interactive remote channel available for customers anytime and anywhere.

Remember, when you sell insurance service you make a promise to your customers to deliver the best level of service to ensure protection of their lives and important things!

We wish you successful projects!

Sincerely, Agilie team.

Mobile technologies greatly influence our life. Mobile app is a good tool to manage health with tasks, reminders, alerts etc. Moreover, mobile apps not only take care of your health, but help you in troublesome situations. A lot of insurance companies develop special&nbsp;insurance apps&nbsp;which make cooperation with customers more convenient and innovative. Modern and intuitive application allows users to use the services of insurance online, as well as to receive information about the company&#39;s services, promotions and locations.

For insurance companies insurance apps and insurance website design is a good opportunity to increase the loyalty of existing customers and to attract new clients.

Insurance Apps and Website Design

At least once in a life each of us has been in a situation when you need to call a taxi in a noisy place, but the high level of noise doesn&#39;t allow calling a dispatcher to book a taxi. Or this situation happens: you&#39;re caught in the rain, you wish to press one button and find yourself in the back seat of a taxi. There are a lot of such cases. On the other hand, every&nbsp;taxi service&nbsp;owner is also interested in automating the process of receiving orders and increasing work efficiency.

All these situations are dealt with by one solution - <a href="/expertise/technology/mobile-development">the development of mobile applications for taxi services</a>, or simply taxi applications.

<img alt="Agilie, mobile applications development company represents Shark Taxi, standalone applications" src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/pictures/17/content_mobile_apps_for_taxi.jpg" />

Benefits from the development &amp; implementation of a taxi management system are obvious:

&bull; Taxi booking in a few clicks that excludes communication with the operator.

&bull; Using GPS to determine customer&#39;s location automatically; this saves time for the driver and client.

&bull; Automatic calculation of mileage and cost of the trip.

&bull; Data about the car and driver is provided to a client at once, and he can track a route of a&nbsp;car, as well as view information about a driver.

Without a doubt, <a href="/blog/step-by-step-guide-on-taxi-app-development-features-and-business-model">taxi service app</a>&nbsp;is a useful tool for city residents, disregarding their&nbsp;status, lifestyle or age.

Estimate the advantages of using a mobile app&nbsp;for calling a taxi service!

Have a nice day!

At least once in a life each of us has been in a situation when you need to call a taxi in a noisy place, but the high level of noise doesn&#39;t allow calling a dispatcher to book a taxi.&nbsp;On the other hand, every&nbsp;taxi service&nbsp;owner is also interested in automating the process of receiving orders and increasing work efficiency.

All these situations are dealt with by one solution -&nbsp;the development of mobile applications for taxi services, or simply&nbsp;taxi applications.

Taxi application is one of the most efficient tools of a taxi management system that can organize a taxi service in a clear and easy way both for clients and taxi drivers.

Taxi Management System

​If you're willing to make a perfect trading app like E-Trade, follow the guidelines of our article.&nbsp;

How To Build a Trading Platform? Follow our advice on the best stock market application development

How To Build a Trading Platform. 5 Things To Know Before You Start a Stock Market App Like E-Trade

How to create a live streaming website? Read all the details in our article!

Wanna know how to create a successful streaming site like Twitch, with 300+ million visits per month?  ➠ Click here to find out all the details!

How to Create a Live Video Streaming Website Like Twitch and Get Your Revenue

Read our article to find out how to create a financial app and make your profit.

Do you want to earn with your own personal finance app? Read our article to find out how

How to Build a Personal Finance App (Updated 2023 Guide) | Agilie

What is the discovery phase, and why do you need it? Read our article to find out the answers!

You’re planning to create a website or application and want it to make you profit as soon as possible, right? In this case, you cannot do without the discovery phase in software development ⚡ But what is the discovery phase of a project, and how to implement it in practice? Read our article to find out the answers ✅

Articles on tech insights