<span style="color: #0d0d0d; font-family: S&ouml;hne, ui-sans-serif, system-ui, -apple-system, 'Segoe UI', Roboto, Ubuntu, Cantarell, 'Noto Sans', sans-serif, 'Helvetica Neue', Arial, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol', 'Noto Color Emoji'; font-size: 16px; text-align: start; white-space-collapse: preserve; background-color: #ffffff;">If you currently earn on mobile apps (or wish to start!), our insightful article will definitely be useful to you.

How to increase mobile app engagement? The question is a top one, for without involving the user in an interaction process you're unlikely to retain him, which leads to fewer earnings ⚡ Interested? Then let's talk about user engagement in mobile apps in great detail  

How to Increase Mobile App Engagement - Complete Guide

When thinking about launching a mobile app, it's important to understand how to reduce software development costs.

Imagine: you want to create a mobile app but your development budget is limited 

How to Reduce App Development Cost

- 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 they are to be blocked 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 

In December 2015, Apple released a new provider API for Apple Push Notification service (APNs). This API is based on the HTTP/2 network protocol and allows app developers to send remote notifications to their app on iOS, tvOS, and OS X devices, and to Apple Watch via iOS.
We&rsquo;ve analyzed the new provider API, and in this article, we&rsquo;ll present a breakdown of its most important features and the benefits this long-awaited update brings to iOS developers.
<h2 style="text-align: justify;">Why we needed this APNs API update</h2>
APNs debuted back in iOS 3 era, and has remained largely unchanged throughout all these years, even despite implementing APNs has always been somewhat problematic for the app developers. Here are only some of the issues that were making the work with APNs too time-consuming and complex:
<ul>
<li style="text-align: justify;">Notifications had to be serialized to a binary format and sent individually using a secure TCP socket.</li>
<li style="text-align: justify;">Sockets required Apple&rsquo;s SSL certificate to be opened in.</li>
<li style="text-align: justify;">All - Development, AdHoc, App Store, and VoIP apps - had to use different certificates.</li>
<li style="text-align: justify;">We had to use a separate binary TCP socket API to check for unsubscribed devices in order to avoid sending future notifications to them.</li>
<li style="text-align: justify;">All errors led to the TCP socket closing.</li>
<li style="text-align: justify;">Error codes were too generalized which made it difficult to identify the exact causes of errors.</li>
<li style="text-align: justify;">A high notification throughput required multiple simultaneous connections to be opened.</li>
</ul>
The new provider API finally fixes all these issues making Apple Push Notifications service much more fast and convenient thanks to HTTP/2 protocol and JSON data interchange format.
<h2 style="text-align: justify;">New features</h2>
The HTTP/2 APNs provider API makes our life as developers much easier by the following things:
<ul>
<li style="text-align: justify;">&nbsp;A JSON-based request-response protocol</li>
<li style="text-align: justify;">APNs now sends 200 Success Response on each notification</li>
<li style="text-align: justify;">Errors are now getting a JSON-string response with detailed error descriptions</li>
<li style="text-align: justify;">Message length increased from 2048 bytes to 4096 bytes, which enables to add extra content to notifications (not just text, but also images and GIFs)</li>
<li style="text-align: justify;">Compression allows to reduce the number of simultaneous connections to sustain a notification throughput</li>
<li style="text-align: justify;">The connection status check with the HTTP/2 PING Frame</li>
<li style="text-align: justify;">Topics support - you can now identify topics (bundle identifiers) for your notification</li>
<li style="text-align: justify;">The <a href="https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/AddingCapabilities/AddingCapabilities.html#//apple_ref/doc/uid/TP40012582-CH26-SW11" target="_blank" rel="nofollow noopener">Universal Push Notification Client SSL Certificate</a> for Development, AdHoc, App Store, and VoIP apps</li>
</ul>
<img style="width: 800px; height: 472px;" src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/attachments/2088/content_http_2_-_1_updated.jpg" alt="APNS notifications delivery service" />
The updated push notifications delivery service&nbsp;protocol
<h2 style="text-align: justify;">How the HTTP/2 protocol makes notifications more effective</h2>
The HTTP/2 is basically an extension of the previous HTTP 1.x standards. This means that, although HTTP/2 eradicates the performance limitations of the previous protocols, the core concepts remain the same, and the developers don&rsquo;t need any app-level changes to update the existing notification systems.
Binary framing layer
The performance enhancements of HTTP/2 are possible thanks to the new binary framing layer. It introduces a more effective way how to encapsulate and transmit HTTP messages between the client and server.
<img style="width: 800px; height: 377px;" src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/pictures/164/content_http_2_-_2.png" alt="HTTP 2.0 binary framing layer" />
Binary framing layer
The binary framing layer splits all HTTP/2 communication into smaller messages and frame, encoding them in binary format. Yet, the apps will be unaware of those changes - all changes happen on a client-server level: while the HTTP semantics remains the same, only the way how it&rsquo;s being transmitted and encoded is now different.
Also, with the new binary framing mechanism, we can say&nbsp;farewell to parallel TCP connections. Now, splitting streams into many interleaved and prioritized frames makes connections persistent and fast since it requires only one connection per origin.
Data exchange mechanism
The new mechanism of data exchange is based on three components: 1) Streams, 2) Messages, and 3) Frames.&nbsp;
All communication goes through a single TCP connection that can carry any number of streams.
Stream is a two-directional flow of bytes that happens during the connection and transmits messages. Each stream carries messages using a unique identifier and optional priority information.
Message is a logical request or response mapped by a sequence of frames.
Frame is the smallest unit of communication in HTTP/2. Each frame contains a header that identifies the stream the frame belongs to.
Hence, the HTTP/2 protocol communication is realized through the exchange of binary-encoded frames which are mapped to messages. Messages, in their turn, belong to particular streams. All these components are multiplexed within a TCP connection and ensure the best performance the HTTP protocol ever had.
Request and response multiplexing
As mentioned above, the binary framing layer in HTTP/2 enables full request and response multiplexing within a single TCP connection: first, the client and the server breaks an HTTP message down into independent frames, then interleave them, and finally reassemble them on the output.
This improvement alone leads to a number of performance benefits for push notifications, including:
<ul>
<li style="text-align: justify;">Interleaving multiple requests and/or responses without blocking on any one</li>
<li style="text-align: justify;">Interweaving the logical streams over a single TCP connection without head-of-line blocking</li>
<li style="text-align: justify;">Using a single connection to deliver multiple simultaneous requests and responses</li>
<li style="text-align: justify;">Removing of the unnecessary HTTP/1.x workarounds that we were using to compensate the previous protocol&rsquo;s shortcomings</li>
</ul>
<img style="width: 800px; height: 294px;" src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/pictures/166/content_http_2_-_3.png" alt="Parallel streams HTTP 2.0" />
Three parallel streams being transmitted between the client and the server within one connection
Header compression
Each HTTP transfer carries a set of headers with metadata that describe the transferred resource and its properties. In HTTP/1.x, headers were sent as plain text &nbsp;adding a considerable weight. In HTTP/2, request and response header metadata are compressed using the HPACK compression format.&nbsp;
To compress headers, HPACK uses two techniques:
<ol>
<li style="text-align: justify;">Encoding the transmitted header fields using a static <a href="https://en.wikipedia.org/wiki/Huffman_coding" target="_blank" rel="nofollow noopener">Huffman code</a>, which reduces their individual transfer size.</li>
<li style="text-align: justify;">Encoding the transmitted header fields using an indexed list of previously transferred values as a reference for the effective reconstruction of the full header keys and values.</li>
</ol>
<img style="width: 800px; height: 527px;" src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/pictures/167/content_http_2_-_4.png" alt="HPACK header compression for HTTP 2" />
HPACK&nbsp;header compression for HTTP/2
<h2 style="text-align: justify;">Conclusion</h2>
Before the update, Apple Push Notifications service was limited by the shortcomings of the HTTP/1.1 protocol. The protocol&rsquo;s forcing to use multiple TCP connections to process multiple requests simultaneously had a huge negative impact on the network performance. The old APNs also required different certificates for different app builds throughout the development process course&nbsp;and was making it almost impossible to track the sent notifications.
These and many other issues were unnecessarily time- and resource-consuming for us as app developers.&nbsp; The new APNs provider API employing HTTP/2 protocol solves all major problems the previous API had, allows to eradicate unnecessary workarounds, greatly increases performance, and reduces the overall development time.
&nbsp;
Further reading on APNs and HTTP/2:
What&rsquo;s New In Apple Push Notification Service / WWDC16
<a href="https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/Introduction.html" target="_blank" rel="nofollow noopener">Local and Remote Notification Programming Guide / Apple Developer</a>
<a href="https://www.smashingmagazine.com/2016/02/getting-ready-for-http2/" target="_blank" rel="nofollow noopener">Getting Ready For HTTP/2: A Guide For Web Designers And Developers / Smashing Magazine</a>
&nbsp;
Also, read about our <a href="expertise/technology/mobile-development" target="_blank" rel="nofollow noopener">iOS</a> and <a href="expertise/technology/mobile-development" target="_blank" rel="nofollow noopener">Android</a> app development services.

In December 2015, Apple released a new provider API for Apple Push Notification service (APNs).&nbsp;

APNs provider API is based on the HTTP/2 network protocol and allows app developers to send remote notifications to their app on iOS, tvOS, and OS X devices, and to Apple Watch via iOS. We’ve analyzed the new provider API, and now present a breakdown of its most important features and the befits it provides to iOS developers.

HTTP/2-Based Provider API for APNS: The Most Important Features And Benefits for App Development

When it comes to <a href="https://agilie.com/expertise/technology/ui-ux-design" target="_blank" rel="noopener">creating animated prototypes for websites</a> and <a href="https://agilie.com/expertise/technology/mobile-development" target="_blank" rel="noopener">mobile apps</a>, our design team normally prefers using tools like <a href="https://www.invisionapp.com/" target="_blank" rel="nofollow noopener">InVision</a> and <a href="https://www.adobe.com/products/aftereffects.html?promoid=KLXLW" target="_blank" rel="nofollow noopener">Adobe After Effects</a>. Nevertheless, we&rsquo;re always open to experimenting and often try alternative UI prototyping tools, especially when we have to deal with unusual tasks.
This time, we decided to explore <a href="https://helpx.adobe.com/muse/kb/adobe-muse-end-of-service.html" target="_blank" rel="noopener">Muse</a>, a website building tool from Adobe. Let&rsquo;s see how it worked out.
<h2 style="text-align: justify;">The case</h2>
The team needed to present a fully functional landing page for an elite eyewear company&rsquo;s website. The page is a long read featuring several scroll transitions (including parallax scrolling effects), a product catalog, and headlines and photos appearing with &ldquo;fade in&rdquo; and &ldquo;fade in up&rdquo; effects.
<h2 style="text-align: justify;">Why Muse?</h2>
Adobe After Effects was simply not the right tool for the task. Although animating such a page with After Effects would take comparatively little time, we still wouldn&rsquo;t have got a fully functional website prototype with working transitions and scroll effects.
InVision, in its turn, doesn&rsquo;t support parallax scrolling effects, and our prototype had to rely on these effects heavily.
So, we needed a tool designed specially for creating responsive websites and able to preview prototypes right in the browser.
&ldquo;Create gorgeous HTML5 websites without writing code,&rdquo; the headline on the Adobe Muse&rsquo;s homepage was saying. It seemed to be exactly what we were seeking for.
Muse allows creating text headlines, paragraphs, buttons, input forms, blocks of media content and more right on the fly. Actually, you can build a whole website from scratch using Adobe Muse, but it can deal with a landing page prototype no worse.
<h2 style="text-align: justify;">Adding content and working with parallax effects</h2>
The landing page mockup was created in <a href="https://www.sketchapp.com" target="_blank" rel="nofollow noopener">Sketch</a>. Then, the content was exported as .svg and .png files which are fully compatible with Muse.
Next, we had to add scroll transition effects to the page. In Muse, working with scroll transitions is operated via the &ldquo;Scroll Effects&rdquo; toolbar that contains motion, opacity, slideshow and animation settings.&nbsp;
<img style="width: 260px; height: 336px;" src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/pictures/157/content_muse_scroll_effects.jpg" alt="" />
Setting motion speed in the Scroll Effects toolbar in Muse
Here, to create parallax scrolling effects in Adobe Muse, as well as &ldquo;fade in&rdquo; and &ldquo;fade in up&rdquo; effects for appearing elements, we needed only to play with motion and opacity settings: the former allows to set the initial and the final values of the scrolling and fade effects&rsquo; speed, and the latter does the same for the animated elements&rsquo; opacity.
It&rsquo;s pretty simple, but it may take some time to experiment with different values&rsquo; combinations before you get a smooth result.
<h2 style="text-align: justify;">Adding CSS animation effects&nbsp;to the prototype</h2>
The &ldquo;Scroll Effects&rdquo; tools in Adobe Muse allow to create smooth and beautiful parallax scrolling effects, but we also needed to include several animated headlines to our prototype which wouldn&rsquo;t depend on the scrolling speed.
To do this, we linked jquery and animate.css libraries to the prototype using the <a href="https://wow.js.org/" target="_blank" rel="nofollow noopener">WOW.js plugin</a>. Here&rsquo;s a video that explains how to do it in detail:
<iframe src="https://www.youtube.com/embed/Vnk_YQv3IPk" width="100%" height="350" frameborder="0" scrolling="no" align="middle"></iframe> &nbsp;
<img style="width: 468px; height: 500px;" src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/pictures/162/content_muse_html.jpg" alt="" />
Muse allows to assign classes to the created elements and to insert an HTML code right into a page and into the &lt;head&gt; container.
<h2 style="text-align: justify;">A few more valuable features</h2>
Adobe Muse also allows to adding anchor tags that allow a user to jump to a specific location on your page. Anchor tags are often used to create a navigation bar for landing pages.
&ldquo;Scroll Effects&rdquo; toolbar is active only when you have a fixed page width. Thus, if you want to make your prototype adaptive and to apply scroll effects to all the elements, you&rsquo;ll need to set and adjust breakpoints. Breakpoints mark the segments of the screen that can change their proportions or disappear completely depending on the screen or the browser&rsquo;s window sizes.
<h2 style="text-align: justify;">Exporting the prototype as a .html/.css file</h2>
As soon as the prototype was ready, it was time to hand it over to our <a href="https://agilie.com/expertise/technology/web-development" target="_blank" rel="noopener">web development</a> team, so they could prepare it for the presentation in the actual web environment.
Adobe Muse can export a prototype as a .html or a .css file, which means that our web developers got a full-fledged website organized as a set of containers. Thus, the developers had only to edit the existing and add new elements.
<img style="width: 493px; height: 500px;" src="https://d12zh9bqbty5wp.cloudfront.net/ckeditor_assets/pictures/163/content_muse_export.jpg" alt="muse file export" />
<h2 style="text-align: justify;">Final thoughts</h2>
Of course, working on this landing page, we weren&rsquo;t able to explore the full potential of Adobe Muse, so, for now, there will be no ultimate conclusion. We continue testing Muse and have already rated it as an alternative to the usual tools we use for creating prototypes for desktop apps and websites.
The tool is not flawless, though. It really lacks libraries for layers&rsquo; animation, the possibility to work with masks, and the &ldquo;Scroll Effect&rdquo; toolbar is not as intuitive as it can be.
Yet, I&rsquo;d recommend trying Adobe Muse if you want to build a prototype functionally close to an actual website and have no experience of using other similar tools - Muse is quite friendly for the newcomers, yet quite functional to appeal an experienced designer.
Links:
<a href="https://helpx.adobe.com/support/programs/support-options-free-discontinued-apps-services.html" target="_blank" rel="noopener">Responsive&nbsp;web design with Adobe Muse</a>
<a href="https://dribbble.com/agilie" target="_blank" rel="nofollow noopener">Our Dribbble page</a>
<a href="https://www.behance.net/agilie" target="_blank" rel="nofollow noopener">Our Behance page</a>

Our design team's first look at how to make a working website prototype with Adobe Muse.

Building a working website prototype with Adobe Muse

How to Build a Website Prototype With Adobe Muse

&nbsp;
According to Tim Cook, Apple Watch is the most personal device ever made by Apple, and we have to admit he is right. As nothing can be more personalized that a gadget that is worn on a wrist and can be additionally set up according to a user's needs and wishes. Besides that, the smart watch gives new ways of interaction that were not possible or demanded on an iPhone. The key task of the Apple Watch is to be useful, discreet and laconic, as they are meant to be used on the go.
Apple Watch runs on watchOS. It is the operaing system developed especially for this device. It is based on iOS and supports applications that are based on Apple WatchKit. Apple company shares a&nbsp;set of all the necessary instruments for making new apps or updating existing ones with developers.
There are different opinions among developers of such applications. On the one hand, it is a brand-new device and it creates new tasks and opens up new possibilities for new types of apps. On the other hand, it is a well-known fact that iOS is quite a reserved system and it has some limitations, which touched Apple watchOS as well. As a result, it may narrow possibilities for developers.
Anyway, more and more companies update their iOS apps and adapt them for Apple watch. Apple Watch apps development becomes more demanded in different sectors of business. Our Agilie team has also started developing apps for watchOS, and recently we have finished working on our Apple Watch application Shot Bucket. It is a Dribbble client that is now available for users in their Apple Watches.
Please visit <a href="https://agilie.com/services">Services</a> page&nbsp;on our website in order to find out more about Apple watch apps development at Agilie.
Subscribe to our blog and please follow us on:
<div style="line-height: 20.8px; text-align: justify;">Dribbble:&nbsp;<a href="https://dribbble.com/agilie" rel="nofollow">https://dribbble.com/agilie</a></div>
<div style="line-height: 20.8px; text-align: justify;">Behance:&nbsp;<a href="https://www.behance.net/agilie" rel="nofollow">https://www.behance.net/agilie</a></div>
<div style="line-height: 20.8px; text-align: justify;">Facebook:&nbsp;<a href="https://www.facebook.com/AgilieTeam/">https://www.facebook.com/pages/Agilie/</a></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="https://agilie.com/contacts">Contact form</a>.

According to Tim Cook, Apple Watch is the most personal device ever made by Apple, and we have to admit he is right.&nbsp;

Apple Watch runs on watchOS. It is the operaing system developed especially for this device. It is based on iOS and supports applications that are based on Apple WatchKit.

Apple Watch App Development

Some years ago mobile internet on the phone has been considered an unnecessary feature, and the most of Internet users were using desktop computers. Now it is left in the past and it is safe to say that it is time for the mobile internet.
Since the start of 2014 when the most of Internet users were choosing mobile access to the world net, it became obvious that in order to make a website effective and attended, an owner has to make it handy and readable both for smartphones/tablets and big screens &ndash; not only PCs but TV-screens with a Smart TV option. Moreover, website optimization for mobile devices becomes a competitive advantage in some business sectors.
In order to help you to decide which type of a site you need and to make it mobile friendly let us have a look at different types of mobile friendly websites &amp; choose the best for you:
Responsive site &ndash; a webpage (URL, HTML, images, etc) remains the same only CSS sets different rules depending on the width of a browser.
Separate mobile site is a website separated from the main one and is focused on smartphones/tablet users. Normally it redirecs mobile users to a special subdomain.
Adaptive website &ndash; it is the most progressive way of creating a website, as its peculiarity is making pages that will be the same readable on devices of any size. Adaptive web design is cheaper for website owners and easier for developers as there is no need to create several website versions for various devices, which would be very ineffective.
Our team creates mobile friendly websites using the solution of <a href="expertise/technology/ui-ux-design">adaptive web design</a> in order to bring users and site owners the best experience and high efficiency.
<div style="line-height: 20.8px;">Follow us:</div>
<div style="line-height: 20.8px;">Dribbble:&nbsp;<a href="https://dribbble.com/agilie" rel="nofollow">https://dribbble.com/agilie</a></div>
<div style="line-height: 20.8px;">Behance:&nbsp;<a href="https://www.behance.net/agilie" rel="nofollow">https://www.behance.net/agilie</a></div>
<div style="line-height: 20.8px;">Facebook:&nbsp;<a href="https://www.facebook.com/AgilieTeam/">https://www.facebook.com/AgilieTeam/</a></div>
<div style="line-height: 20.8px;">Twitter:&nbsp;<a href="https://twitter.com/agile_ninjas" rel="nofollow">https://twitter.com/agile_ninjas</a></div>
<div style="line-height: 20.8px;">&nbsp;</div>
<div style="line-height: 20.8px;">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 style="line-height: 20.8px;" href="contacts">Contact form</a>.</div>

Some years ago mobile internet on the phone has been considered an unnecessary feature, and the most of Internet users were using desktop computers.&nbsp;

Adaptive web design is cheaper for website owners and easier for developers.

Common types of mobile friendly websites

Alexander Volk, our Head of Design, shares transformative insights in his articles, which turn into vital resources for both rising and experienced designers.

Alexander Volk - Head of Design Department at Agilie

Alexander Volk

For its readers, Sergey's articles contain guidelines, strategies, methods, and instruments that are crucial to mastering diverse technologies.

Sergey Melashich - CTO at Agilie

Sergey Melashich

Sergeys’ articles describe success in the context of continued growth in today’s modernized environment as well as the emerging trends in the technological sector.

Sergey Gladun - CEO & Founder at Agilie

Sergii Gladun

Michael writes articles about design and the creation of making solutions which are efficient, good and unique in concept, design, fabrication.

Michael Liptuga - Delivery Director at Agilie

Michael Liptuga

The various articles written by Alina clearly expose a valuable approach to developing an effective development team and convey the comprehension of translating complex processes into beneficial solutions.

Alina Danets - COO at Agilie

Alina Danets

Kate crafts article through her strategic thinking lens to respond not only to the current market but also to act proactively and construct excellent and sound financial products or services that can fulfill the clients’ expectations.

Kate Myronenko - Head of Business Unit at Agilie

Kate Myronenko

It is quite likely that readers armed with Sergii's in-depth knowledge of iOS technologies will develop applications that bear great consideration for Apple’s environmental guidelines and at the same time are creative and innovative. 

Sergii Avilov - Head of IOS Department at Agilie

Sergii Avilov

Artem Tarasenko has a lot of experience in React and is the author of many articles and tutorials that describe complex approaches and workflows in front-end development.