Effective team communication is an essential element to successful business life and a high level of productivity.&nbsp;

How to improve communication within a team? The question is very important: whatever the size of your company is, effective team communication will be an essential element to successful business life ✌ Interested? Then read our article to find out the best online tools for communication and collaboration 

How to Improve Team Communication with Digital Technologies

Our team is constantly working with various web frameworks, both new ones, which have just appeared on the IT market, and old ones that have already gained a certain reputation. We test such solutions, try to better or adapt them, and then we share our experience with you. This time we're going to discuss popular Angular dialog windows and our attempts to improve them.
We&rsquo;ll explain to you how to implement a dialog window in the most efficient way. You'll find a lot of details on Angular, read how to open dialogs without file size increasing, and so on.
<h2 dir="ltr" style="text-align: justify;">AngularJS or Angular?</h2>
AngularJS has a pretty impressive history that goes back over 10 years (since 2009). The framework was initially developed by Adam Abrons (who is no longer part of the project) and Mishko Hevery (who keeps improving the solution in question with the assistance of Google and its highly qualified employees).
If some web developers consider HTML &ldquo;an enemy to fight against&rdquo;, the creators of Angular.JS decided to take a different path. They expanded the possibilities of HTML syntax by introducing additional directives, which are one of the key features of AngularJS.
In addition, AngularJS developers believe that the code should be covered as much as possible with tests (in order to avoid future bugs). Therefore, the framework was initially friendly in writing tests.&nbsp;
And yet, despite a number of advantages, AngularJS had a few performance disadvantages (and not only performance ones). Therefore, in the spring of 2014, it was decided to completely update and improve the framework (so to speak, create AngularJS 2.0).
And since the new version, released in September 2016, was written in TypeScript and differed from the original one, it was renamed as Angular.&nbsp;&nbsp;
<h3 dir="ltr" style="text-align: justify;">JavaScript or TypeScript?</h3>
As you already understood, AngularJS is a JS-based framework that greatly simplifies the process of creating web resources. The fact is that almost any web developer (possessing JS knowledge at least at the basic level) can use AngularJS in his work.
Angular, on the other hand, is written in TypeScript, which, although derived from JS, has its own distinctive features. In particular, TypeScript hasn't abandoned the inherent concepts of object-oriented languages. This approach makes it much easier to write complex programs; also, it's more convenient to maintain, scale, and test them.
<div class="blog-banner__wrapper blog-banner__wrapper--small"><a class="blog-banner__link" style="background-image: url('https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/attachments/3920/small_incut.png');" href="https://agilie.com/blog/why-is-it-worth-to-choose-ruby-on-rails-for-your-startup" target="_blank" rel="noopener"><img class="image-incut-hide" src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/attachments/3920/small_incut.png" alt="" width="850" height="180" /></a>
<div class="blog-banner__container">
<div class="blog-banner__title">Why should you choose Ruby on Rails to start a new web project? Read our article to find out!</div>
</div>
</div>
Now let's move on to our example. During development, we, surely, have to deal with various modal dialogs (and non-modal dialogs). And sometimes we may encounter certain difficulties. Trying to solve such problems often leads to new web solutions. And you, too, can take advantage of the results of our efforts.
Let&rsquo;s take a closer look at the issue.
<h2 dir="ltr" style="text-align: justify;">Angular Dialog Box</h2>
Angular isn't a &ldquo;dead&rdquo; framework (figuratively speaking), developers continue to work hard on improving it by adding new features and elements to it. However, in some ways, its functionality differs from that offered by AngularJS. Among other things, let's pay closer attention to the dialog window (popup).
We propose to consider 2 popular ways to implement a dialog box, namely: <a href="https://github.com/shlomiassaf/angular2-modal" target="_blank" rel="nofollow noopener">angular2-modal</a> and <a href="https://github.com/pleerock/ngx-modal" target="_blank" rel="nofollow noopener">ngx-modal</a>. What can they do?
<h2 dir="ltr" style="text-align: justify;">What Can These Components Do?</h2>
<h3 dir="ltr" style="text-align: justify;">The ability to open a dialog box directly</h3>
Resort to these components to open the dialog boxes with the indicated template from the component you require.
The whole implementation process is extremely simple: import the service you need and call the appropriate method to perform the action. This is usually enough to open a dialog box directly. If not, use a base component to wrap your template, then call the Open function (using its link).
It looks as follows:
<pre><code class="language-javascript">//Option 1. Calling from the component



openDialog() {



&nbsp;&nbsp;&nbsp;this.dialog



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.body(&lsquo;&lt;h4&gt;My first dialog window&lt;/h4&gt;&rsquo;)



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.open();



}



//Option 2. Wrapping the dialog window in the base component



&lt;button (click)="myDialogWindow.open()"&gt;open dialog window&lt;/button&gt;



&lt;modal #myDialogWindow&gt;



&nbsp;&nbsp;&nbsp;&nbsp;&lt;!-- Your dialog window HTML code --&gt;



&lt;/modal&gt;</code></pre>
<h3 dir="ltr" style="text-align: justify;">Customization</h3>
It is logical to assume the components of the dialog window should offer some basic configuration to manage it. Here are just a couple of key examples:
<ul style="list-style-type: disc;">
<li dir="ltr" aria-level="1">
control of the size of the dialog box;
</li>
<li dir="ltr" aria-level="1">
button to close, hide, or open it;
</li>
<li dir="ltr" aria-level="1">
the chance to close the box by outside click;
</li>
<li dir="ltr" aria-level="1">
and so on.
</li>
</ul>
The purpose of all these configurations is to help you customize the dialog window to suit your needs.
It allows you to get a custom dialog box, which is a big advantage, isn't it?
<h2 dir="ltr" style="text-align: justify;">What Do These Components Lack?</h2>
Customizable Angular dialogs are a good thing, but you shouldn't forget about some of the disadvantages of these components, namely...
<h3 dir="ltr" style="text-align: justify;">Dialog boxes as dynamically created elements</h3>
As you already understood, some components require passing HTML templates to a specific function, while others serve to wrap the templates (as we wrote above).
Let&rsquo;s take a closer look at each case.
<ol style="list-style-type: decimal;">
<li dir="ltr" aria-level="1">
You insert the dialog into your HTML code when called. But you should bear in mind that it&rsquo;s not about a single (separate) element, and this fact goes against the concept of Angular apps.
</li>
<li dir="ltr" aria-level="1">
So, you used the base dialog window component as a wrapper for the template, but thereby you increased the file HTML size (since the template immediately penetrates the code). As a result, the web page takes longer to load, which annoys the user. In addition, there is the problem of resetting data (after all, the dialog is just hidden, not deleted after it has been closed).
</li>
</ol>
By wisely using the capabilities of Angular, you get the chance to dynamically insert elements into templates of other components. That is, a component instance is being created (and drawn) ONLY when the function has been called. And it gets removed on close (which can be customized as desired)
<h3 dir="ltr" style="text-align: justify;">Data transmission</h3>
Besides, no one would mind the ability to transmit various kinds of data to the dialog box. Say, how about lines, arrays, objects, and more?
<h2 dir="ltr" style="text-align: justify;">Ng2-dialog-window: Our Improved Solution</h2>
Our team successfully applied ng2-dialog-window (1st version); what's more, we managed to reduce the impact of the above-described disadvantages. And we're not going to relax our efforts! We'll keep working on bettering the solution.
<h3 dir="ltr" style="text-align: justify;">A quick guide to using ng2-dialog-window</h3>
1) First, decide from which component you are going to call the dialog box. Connect Ng2DialogWindowService to it and call the openModal method.&nbsp;
<pre><code class="language-javascript">constructor( private dialog: Ng2DialogWindowService, private viewContainer: ViewContainerRef) {



}



openModal() {



&nbsp;&nbsp;&nbsp;&nbsp;this.dialog.openModal(this.viewContainer, {component: YourDialogWindowComponent})



}</code></pre>
2) Add your dialog window component to the entryComponents​
<pre><code class="language-javascript">@NgModule({



&nbsp;&nbsp;&nbsp;//...



&nbsp;&nbsp;&nbsp;entryComponents: [



&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;YourDialogWindowComponent



&nbsp;&nbsp;&nbsp;],



})</code></pre>
3) Now is the time to extend your component from Ng2DialogWindowComponent. Such a step would help you inherit base methods; therefore, you'll be able to use ng2-dialog-window-component tag to wrap the template.
P.S. We guess Angular doesn't have an easier way to inherit other components styles. Let us know if you consider us wrong (of course the situation could have changed for the better since this article was written).
<pre><code class="language-javascript">@Component({



&nbsp;&nbsp;&nbsp;&nbsp;selector: 'my-dialog-window',



&nbsp;&nbsp;&nbsp;&nbsp;template: '&lt;ng2-dialog-window-component&gt;&lt;!-- Body of dialog window --&gt;&lt;/ng2-dialog-window-component&gt;'



})



export class YourDialogWindowComponent extends Ng2DialogWindowComponent {



}</code></pre>
If you need more details, click <a href="https://github.com/agilie/ng2-dialog-window" target="_blank" rel="nofollow noopener">here</a> and read the documentation at length.
<h2 dir="ltr" style="text-align: justify;">Summary</h2>
We showed you some Angular dialog box examples and described our experience with them and their adaptation. And you&rsquo;re welcome to take full advantage of these components; maybe you can offer some bettering too, can&rsquo;t you?
<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/3928/contact_us_3.jpg');" href="https://agilie.com/contacts" target="_blank" rel="noopener"><img class="image-incut-hide" src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/attachments/3928/contact_us_3.jpg" alt="" width="850" height="300" /></a>
<div class="blog-banner__container">
<div class="blog-banner__title">Do you have any questions? We&rsquo;re happy to answer them!</div>
</div>
</div>
&nbsp;

Angular is an actively developing framework with new components being created for it every day.&nbsp;

Looking for solutions to implement a dialog window as simple as possible? We want to share our experience with this issue ✅ Follow the link and read the article on сustomizable Angular dialog boxes ☝


Popular Angular Dialog Windows and How We Tried to Improve Them

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">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

Blockchain has become a paradigm shift that changes the operations of different industries. Nevertheless, like any other disruptive technology, a lot of myths and misconceptions have appeared. We should differentiate between fact and fiction to use blockchain technology effectively and responsibly. We can better understand what blockchain is (and isn&rsquo;t), how it functions, and the varied applications it holds besides cryptocurrencies by clarifying these misconceptions.
<div id="form-description" class="form-description" data-title="Key Takeaways" data-text="Blockchain is not just about Bitcoin; it is the technology that can transform different fields. 

Blockchains are strong but not flawless, and being aware of the possible weak sections is a very important thing in keeping the network safe.

Educational investment and partnerships with software development experts are the main factors for businesses that will use blockchain technology.">
<div class="form-description-title">Key Takeaways</div>
<ul style="text-align: justify;">
<li dir="ltr" aria-level="1">
Blockchain is not just about Bitcoin; it is the technology that can transform different fields.&nbsp;
</li>
<li dir="ltr" style="text-align: left;" aria-level="1">
Blockchains are strong but not flawless, and being aware of the possible weak sections is a very important thing in keeping the network safe.
</li>
<li dir="ltr" aria-level="1">
Educational investment and partnerships with software development experts are the main factors for businesses that will use blockchain technology.
</li>
</ul>
</div>
<h2 dir="ltr" role="presentation">&nbsp;Myth 1: Blockchain and Bitcoin Are the Same</h2>
Among the most common myths about blockchain technology is the confusion between the blockchain and Bitcoin. Blockchain and Bitcoin were created simultaneously, so they are widely believed to be the same thing. However, we must understand that blockchain is a much broader term. It is the technology that created Bitcoin. While Bitcoin is indeed the first and most famous application of this technology, equating the two is like saying that Google is the Internet.
Blockchain is a decentralized digital ledger technology (DLT) that records transactions across multiple computers so that the records cannot be altered retroactively, without the alteration of all subsequent blocks and the consensus of the network.
This makes blockchain a naturally secure and transparent method of data and transaction recording.&nbsp;
Bitcoin is a type of digital currency based on blockchain technology and used for secure, anonymous, and decentralized financial transactions. The blockchain of Bitcoin acts as a public ledger for all the transactions in the Bitcoin network, thus, it is possible to transfer digital currency securely without the use of intermediaries like banks or governments.&nbsp;
Blockchain technology can be much broader than purely financial transactions. It can be used in different industries with various aims. Nowadays, many businesses are studying how blockchain can improve their operations (read more about <a href="https://agilie.com/blog/enterprise-blockchain-development-how-businesses-derive-benefits" target="_blank" rel="noopener">enterprise blockchain development</a> and <a href="https://agilie.com/blog/enterprise-blockchain-development-how-businesses-derive-benefits" target="_blank" rel="noopener">enterprise-grade blockchain development</a>).

Here are a few examples:
Healthcare: Blockchain can guarantee the safety of medical records storage and sharing. Thus, they are only available to authorized personnel and patients and lead to quicker diagnosis and treatment.​
Financial Services: Blockchain is a viable solution for international payments, real-time settlements, and improving transaction transparency and security.
Digital Identity:&nbsp; Blockchain can correct identity theft and fraud by adding digital identities that cannot be changed. For example, Estonia's e-Residency program is the first of its kind, a government-issued digital identity that allows entrepreneurs from anywhere in the world to operate and conduct business online in the EU.
Real Estate: Blockchain can simplify property transactions such as sales, leasing, and financing by reducing paperwork and improving transparency.
<a class="incut--wrap" style="transition-delay: 0s;" href="https://agilie.com/blog/the-evolution-of-blockchain-from-bitcoin-to-business-applications" target="_blank" rel="noopener" aria-label="incut"><img style="height: 344px; width: 778px;" src="https://d3pxw3l8cozu05.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1716280829344.png" width="100%" height="100%" />Learn more about the evolution of Blockchain from Bitcoin to business applications.</a>
<h2 dir="ltr">Myth 2: Blockchain Transactions Are Always Anonymous</h2>
A frequent mistake people make about blockchain technology is that it is automatically anonymous to its users. However, the truth is more nuanced. Blockchain transactions are not strictly anonymous but pseudonymous.
Pseudonymity means that a user's identity is not directly tied to their blockchain transactions but rather to a digital pseudonym, typically a public key or a blockchain address. These addresses are like a sequence of letters and numbers, giving privacy but not total anonymity.
In contrast, anonymity would mean that the transactions are entirely disconnected from any identity, even a pseudonym, making them untraceable to the user. Blockchain does not usually provide this level of anonymity because the transaction history of each blockchain address is visible to anyone who accesses the blockchain.
Most blockchains are open ledgers, meaning that all transactions are visible to anyone who wishes to view them. This level of transparency ensures that while users' identities are not directly exposed, their transaction histories and patterns can be analyzed.<span style="font-size: 11pt; font-family: Roboto, sans-serif; color: #000000; background-color: transparent; font-weight: 400; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-alternates: normal; font-variant-numeric: normal; font-variant-east-asian: normal; font-variant-position: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;"> 
<img src="https://d3pxw3l8cozu05.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1716280901953.png" />
While basic blockchain transactions offer pseudonymity, several enhancements and tools can increase privacy:
1. Mixing Services: Services like CoinJoin allow multiple users to combine their transactions into a single transaction with multiple inputs and outputs. This mixing blurs the traceability of any single coin, making it more difficult to link wallets with identities.
2. Privacy-Focused Cryptocurrencies: Some cryptocurrencies, like Monero and Zcash, are designed specifically to enhance privacy. Monero uses ring signatures and stealth addresses to hide the transactions&rsquo; origins, amounts, and destinations. Zcash allows users to shield transactions completely through its zk-SNARKs technology, which enables transactions to be verified without revealing the sender, receiver, or amount.
3. Use of Multiple Addresses: Users can increase their privacy by using multiple wallets or addresses, dispersing their transactions across several points, which makes it more challenging to link them to a single identity.
<a class="incut--wrap" style="transition-delay: 0s;" href="https://agilie.com/blog/blockchain-tech-trends-how-to-stay-ahead-of-the-curve" target="_blank" rel="noopener" aria-label="incut"><img style="height: 344px; width: 778px;" src="https://d3pxw3l8cozu05.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1716280997458.png" width="100%" height="100%" />Explore key blockchain technology trends and stay ahead in its innovation with insights and practical examples.</a>
<h2 dir="ltr">Myth 3: Blockchains Are Unhackable</h2>
The idea that blockchains are completely unhackable is a frequently held misconception that can cause a dangerous level of complacency in security measures. While blockchain technology does offer robust security features, it is not immune to vulnerabilities. Knowing the security features employed and the situations in which breaches happen is very important for anyone who wants to use blockchain for their business.
Blockchain technology secures data through several mechanisms:
Cryptography: Every transaction on a blockchain is secured using cryptographic algorithms, which ensure that data can neither be altered nor read without the appropriate cryptographic key.
Decentralization: By distributing copies of the ledger across a network, blockchain reduces the risk of a single point of failure that could compromise the entire system.
Consensus Protocols: Blockchains use various consensus mechanisms, like Proof of Work (PoW) or Proof of Stake (PoS), to agree on the validity of transactions. These protocols prevent a malicious actor from changing even a single aspect of the blockchain.
<a class="incut--wrap" style="transition-delay: 0s;" href="https://agilie.com/expertise/fintech/blockchain-software" target="_blank" rel="noopener" aria-label="incut"><img style="height: 344px; width: 778px;" src="https://d3pxw3l8cozu05.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1716281102044.png" width="100%" height="100%" />Learn more about our blockchain software development services.</a>
Despite these security measures, there are scenarios where blockchains can and have been compromised.
<h3 dir="ltr">Scenarios Under Which Breaches Have Occurred</h3>
51% Attacks: This type of attack happens when a single entity gains control of more than 50% of the network&rsquo;s mining hash rate or stake, allowing them to manipulate transactions and potentially double-spend coins.&nbsp;
Code Vulnerabilities: <a href="https://agilie.com/blog/secure-smart-contract-design-best-practices-in-solidity-programming" target="_blank" rel="noopener">Smart contracts</a>, which are self-executing contracts with the terms directly written into code, can contain vulnerabilities. One of the most famous incidents is the DAO attack on the Ethereum network. Hackers exploited a vulnerability in the DAO (Decentralized Autonomous Organization) smart contract code to siphon off one-third of the DAO&rsquo;s funds.
Phishing and Social Engineering: End-user security is often the weakest link in a blockchain system. Phishing attacks can allow attackers access to blockchain assets, bypassing network security measures, to steal private keys or wallet credentials.
<img src="https://d3pxw3l8cozu05.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1716281254703.png" />
<h2 dir="ltr" style="text-align: justify;">Conclusion</h2>
The blockchain technology is often seen as highly popular and muddled at the same time.&nbsp; Falsified myths are only part of the misconceptions that can mislead such a fantastic technology. Similarly, proper professional knowledge and strategy can help blockchain perform to its potential in various fields.&nbsp;<a href="https://agilie.com/blog/your-own-cryptocurrency-from-scratch-everything-you-need-to-know-to-create-your-cryptocurrency" target="_blank" rel="noopener">Building your own cryptocurrency</a> can be a strategic move for businesses seeking to innovate and tap into new digital markets.
At <a href="https://agilie.com" target="_blank" rel="noopener">Agilie</a>, we understand that dealing with a complex environment is also a significant challenge. This is why we create powerful blockchain systems and wish to educate our clients regarding the breadth of blockchain-utilizing services. Therefore, such solutions can be tailored to your industry's concrete necessities and problems.
<a class="incut--wrap" style="transition-delay: 0s;" href="https://agilie.com/contacts" target="_blank" rel="noopener" aria-label="incut"><img style="height: 344px; width: 778px;" src="https://d3pxw3l8cozu05.cloudfront.net/images/f9e66e179b6747ae54108f82f8ade8b3c25d76fd30afde6c395822c530196169-1716281316627.png" width="100%" height="100%" />Contact us to find out how our blockchain development services can help you achieve your goal.</a>

Discover the truths about blockchain technology as we debunk common myths and clarify its applications to empower businesses with informed integration.

Discover the truths about blockchain technology as we debunk common myths and clarify its applications to empower businesses with informed integration.

Blockchain Myths Debunked: Separating Fact from Fiction

Read about the factors that influence accounting app development costs.

Read about the factors that influence accounting app development costs.

Costs and Time of Accounting App Development | Agilie

Discover the factors that influence fintech app development costs.

Learn about the factors that influence fintech app development costs.

Factors that influence fintech app development costs | Agilie

Read about the essence and development stages of a Peer-to-Peer lending app.

Read about the essence and development stages of a Peer-to-Peer lending app.

Guide on how to develop a P2P lending app from scratch | Agilie

Analyze the development process of the loan application.&nbsp;

Analyze the development process of the loan application.

Guide on How to Build a Loan App | Agilie

Explore successful real estate blockchain startups and the development process of blockchain property app.

Explore successful real estate blockchain startups and the development process of blockchain property app.