<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rita Tavares on Medium]]></title>
        <description><![CDATA[Stories by Rita Tavares on Medium]]></description>
        <link>https://medium.com/@rita.tavares?source=rss-9d31f287891d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zZ05wwD1SycxlswLm_Z7Kg.png</url>
            <title>Stories by Rita Tavares on Medium</title>
            <link>https://medium.com/@rita.tavares?source=rss-9d31f287891d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:07:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rita.tavares/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Strategies To Increase Your App’s Engagement Rate]]></title>
            <link>https://medium.com/airapps/strategies-to-increase-your-apps-engagement-rate-375475a564a9?source=rss-9d31f287891d------2</link>
            <guid isPermaLink="false">https://medium.com/p/375475a564a9</guid>
            <category><![CDATA[application]]></category>
            <category><![CDATA[engagement]]></category>
            <category><![CDATA[mobile-app-publishing]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Rita Tavares]]></dc:creator>
            <pubDate>Mon, 08 Mar 2021 15:10:34 GMT</pubDate>
            <atom:updated>2021-03-08T15:10:34.539Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YJdcTkXSrfrUi-yVDaDItg.jpeg" /></figure><p>Engagement is defined by how long the users stay inside your app, and how many times a day they open it. And how do you keep the user engaged? By extracting the right data you can determine the best path to take, but if you don’t have that data yet, there are some strategies that will surely make a difference:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wt37iwfyRLjhhBDiEw0xJQ.jpeg" /></figure><h3>Welcome New Users</h3><p>You don’t get second first impressions, so it’s important to make it count. When a new user first opens your app it’s important that you teach them how it works, where they can start, and what to do if they need help. This is why onboarding is so important, and the ideal place for you to do that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hy98q9q9Xg0XtFk-Dzz18Q.jpeg" /></figure><h3>Present The Benefits Through Onboarding</h3><p>Explaining the features you have is good, but telling the user the benefits he will get is even better. Focus more on the value each feature provides instead of simply describing them because if the user doesn’t understand the benefits he won’t use it. Example: What do all those features allow the user to do? Be healthier, save time, be more productive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YTtPw-B0CXiBQXEammUeMQ.jpeg" /></figure><h3>Provide Real-Time Support</h3><p>Most of the apps and online services are starting to implement strategies to attend to the user’s needs in real-time. This can be for example bots or live chats. Providing customer support will improve general engagement, since any questions or doubts that were stopping the user from proceeding, can be answered right away. Of course, not all of your users drop because of questions or doubts, but having this aid at hand will only be beneficial.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2N10aFDWIzT7oQa9d6WY4Q.jpeg" /></figure><h3>Offer New Content</h3><p>Updating your app regularly is good to keep users engaged because what’s new and interesting will stop being so after a while. Be careful with the updates since they should be meaningful and provide value to the end-user, instead of just being something new but that they would never use. Make users want to stick around by making them see that you are dedicated to improving their experience and providing new content and value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ri0EDoi2RKaOKM2V4g21Bw.jpeg" /></figure><h3>Use Push Notifications</h3><p>Before you start thinking about the content of the notifications, you need to make the user more eager to allow them first. Before the permission is displayed you could display your screen, where you state all the benefits the user will get if he chooses to allow them. Create a view with curated illustrations for example, and take this chance to speak to your users more personally.</p><p>If they do allow push notifications you can take this chance to re-engage them in case they spent very little time on your app, and didn’t get the chance to try your most valuable features that could’ve probably made them stay. It’s important that you separate your users into different cohorts (groups) and target your messages specifically for each one of those groups.</p><p>Personalize your notification’s content according to each of those group’s needs, for example, based on their last activity inside your app, their age, demographics, etc. In case your app offers a subscription, you can use the notifications to present the users with a limited-time offer that would catch their attention. Don’t forget to focus on the benefits that subscribing to your app would bring them. Another good strategy is telling your users about new updates you have been working on that will again, provide them real value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0daYT28vlysjGVNqPYKOxQ.jpeg" /></figure><h3>Build A Community</h3><p>A great lot of the apps and games most people use are now shifting towards building this community with their users. It could be an online forum where people interact with each other, or it could be a place where they speak to you about improvements and general feedback. This interaction could prevent them from leaving negative reviews on the app store because they would come to this forum to speak to you first. But it doesn’t always have to be an interacting community where people talk to one another or with you, it could be something like displaying the users that are online using your app right. People would still get this feeling of being part of a community but without the need to speak.</p><h3>Wrap-Up</h3><p>Investing in acquiring new users is not enough if you see them drop after the first day. You must tackle your app’s engagement and retention rates to really make that investment count. Check out my article about the <a href="https://medium.com/airapps/retention-improving-guide-step-by-step-dbc2178e3cbe">Steps Of Improving User Retention</a>, and my colleague <a href="https://medium.com/u/e8e22134e223">Carmine Acierno</a>’s <a href="https://medium.com/airapps/why-90-of-users-are-leaving-your-app-on-the-first-day-a-guide-to-increase-retention-rate-25c187a3d1f3">Guide To Increase Retention Rate</a> if you want to know more about the subject. I hope you enjoyed it, thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=375475a564a9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/airapps/strategies-to-increase-your-apps-engagement-rate-375475a564a9">Strategies To Increase Your App’s Engagement Rate</a> was originally published in <a href="https://medium.com/airapps">Air Apps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Retention Improving Guide — Step by Step]]></title>
            <link>https://medium.com/airapps/retention-improving-guide-step-by-step-dbc2178e3cbe?source=rss-9d31f287891d------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbc2178e3cbe</guid>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[retention]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[engagement]]></category>
            <category><![CDATA[mobile-app-publishing]]></category>
            <dc:creator><![CDATA[Rita Tavares]]></dc:creator>
            <pubDate>Tue, 23 Feb 2021 16:41:12 GMT</pubDate>
            <atom:updated>2021-02-24T14:58:37.388Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Stop Losing Users — Boost Your App Retention With This Step-By-Step Guide</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*plF3pUBuWpL_dgHGyFIryw.jpeg" /></figure><p>Retention is a very important concept when speaking about improving an app. If you want to take your app to the next level, you need to retain your users. Keep them interested enough to make them want to keep coming back.</p><p><strong>Let’s structure the process:</strong><br>- So how do you know if your users are coming back to the app? You need information. <br>- How do you get this information? With analytics.<br>- How do you receive the analytics? By implementing trackers inside your app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TQt8E-AtXx66_wkim9tehA.jpeg" /></figure><h3>About Trackers</h3><p>Trackers are like triggers — the user performs an action and activates this trigger that will send the information back to you. You can track the user’s actions depending on where and when you place these triggers. Once you place the “traps” you can start analyzing in which phase they are <em>escaping from you</em>.</p><p>There are different types of trackers: the ones that come from taps, and the ones that don’t. Example 1: First time opening the app; Example 2: Tapping the Register button.</p><p>Take your time during this decision process, because this first step is crucial for you to get the right and most valuable information.</p><h4><strong>How To Start</strong></h4><p>You can start by displaying your app’s views next to each other, and separate them by features or categories. Take a deep look into your UI and decide which events you would like to track: for example, if you have a Sign In/Register view, you might want to track if the users skip this process (if possible), whether they prefer to register with their Apple or Google account, and how long does this process take. Tracking the time here could be beneficial — if the users take a bit too long to complete this flow maybe some tweaks could be made to facilitate the process.</p><p>If you have a tab bar, a menu, or a lot of options on your home view, you could add trackers to each of those buttons and see which ones are pressed more often and the ones that get very little attention from your users.</p><p>After mapping out where the trackers should go, don’t forget to name them. Create a file with the trackers’ names, and a brief description to be shared amongst the designers and developers. The developers will proceed to implement the chosen trackers, but this file is important to keep since you will need the tracker’s names to call them from inside the analytics software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eT5j-Fb9veTk-b2WmWMdNQ.jpeg" /></figure><h3><strong>Analyzing the information</strong></h3><p>After having your trackers implemented, wait a week or two for the information to start gathering inside your dashboards, and this way you can extract more meaningful information from them.</p><h4>How To Start</h4><p>The best way to start is by writing down a few questions you want to answer. Continuing with the Register example, you might want to answer: do my users prefer to enter an email and password manually or Register through another platform? How long do they take to complete this Register process? How many users tap Sign In vs Register?</p><p>The options are endless, so you need to decide what you want to answer and prioritize those questions because maybe some answers will greatly influence your product, while others not so much.</p><p>Find out where your users drop the flow, drop the app, which features they use most, which ones they use less, and for how long. After you have these bits of information you can start grouping your users inside cohorts (audiences on google analytics).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S4P3Lb7z5JXvJk6-NXZUCg.jpeg" /></figure><h4>What Are Cohorts?</h4><p>Cohorts are groups of people that share the same characteristics. And what characteristics are these? The ones <strong>you</strong> define. You can create a cohort (group) of users who Register, as opposed to those Signing In, then create a cohort of people who Register using their Google account details. As you can now realize, some people will be inside both of these cohorts.</p><h4>What Are Cohorts For?</h4><p>By grouping people inside cohorts, you can perform specific actions tailored to each one of these cohorts. Sending push notifications to the cohorts of people who haven’t used your app in the last 2 weeks or sending in-app messages to users who never opened a specific feature in your app could help retain them in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oXAJnPwKMVRRSPCS7oG-hA.jpeg" /></figure><h3>Taking Advantage Of The Data</h3><p>The data you extract isn’t only meant to make cohorts, although this is also very useful. If you want to improve the retention inside your app you need information about how the app is performing now to compare it with the information about how the app is performing after the design changes.</p><p>How many users are covering the flows you had envisioned for them? How many seem to be struggling with a certain view? You need to sketch out possible solutions for the UI and UX of these views in order to improve the user’s experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oW242RHSffN6bcY_kuSXuQ.jpeg" /></figure><h3>Improving The App’s Experience</h3><p>Now that you have the data about how each of your views and features are performing, it’s time to address the known problems. List all the problems you see the users are having with your app (according to the information you previously gathered and analyzed) and prioritize them. Start by sketching ideas to solve the major ones, and while the developers are implementing the first changes, you can start tackling the secondary ones.</p><h4>Test and Iterate</h4><p>Even if you believe you have found the solution for your user’s problems, never settle. Only the numbers can provide the certainty you need to believe the problem is solved (or at least it has a significant improvement). After the changes have been implemented, test them with your users and see how the numbers change. If they got worse, or there were no significant changes, try out different solutions. Don’t stop testing hypotheses until the numbers confirm that you have found a possible solution.</p><p>If you want to know of some strategies on how to increase user retention, check out <a href="https://medium.com/@cacierno/25c187a3d1f3">this article</a> made by my teammate <a href="https://medium.com/u/e8e22134e223">Carmine Acierno</a>.</p><h3>Wrap-Up</h3><p>It’s hard when you put all your effort into an app but then people are not feeling like coming back to it. Improving user retention is a hard subject to tackle, given the fact that the tools we have can only allow us to analyze data, but not provide a concrete solution. That is up to <strong>you</strong>. With the knowledge at hand and your creativity, you have the hard task to find out how to address the known issues by yourself. I hope this article can guide you on your long but exciting journey of improving your app’s retention. Thank you!</p><p><strong>Rita Tavares</strong><br>Lead UI/UX Designer at Air Apps</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbc2178e3cbe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/airapps/retention-improving-guide-step-by-step-dbc2178e3cbe">Retention Improving Guide — Step by Step</a> was originally published in <a href="https://medium.com/airapps">Air Apps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[iOS Navigation Bar Design Guide]]></title>
            <link>https://medium.com/airapps/ios-navigation-bar-design-guide-b22d107bace4?source=rss-9d31f287891d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b22d107bace4</guid>
            <category><![CDATA[mobile-app-publishing]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Rita Tavares]]></dc:creator>
            <pubDate>Wed, 09 Dec 2020 18:29:21 GMT</pubDate>
            <atom:updated>2020-12-09T18:29:21.227Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vx0brc71QAk7YGI6-j55vQ.jpeg" /></figure><p>As UI/UX Designers we come across a lot of elements that are made easy to use by various design tools. However, they are only visual and not all of us understand the depth and functionality behind a static UI element. That is what this article is here for. The <a href="https://developer.apple.com/design/human-interface-guidelines/ios/bars/navigation-bars/">iOS Navigation Bar</a> has been with us since the first iPhone launch and has since been evolving, but before diving deep into the Navigation Bar we should first take a better look at the app architecture — more specifically — its navigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e6zD9_3pZMkXp1v1ufBjHw.jpeg" /></figure><h3>Hierarchical Navigation</h3><p>The Hierarchical navigation style is the one used on Navigation Bars. In this style, the user moves from one screen to another, and the only ways to navigate are by going back or forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jsv9KNz-EchIJpiOxGBmkw.jpeg" /></figure><h3>Navigation Bar Hierarchy</h3><p>The navigation bar manages a parent and its child views, that are all connected. This means that any changes made to either the parent or the children will affect all the views. For example, the removal of the default navigation bar background that is very useful for a smooth display of the content scroll will be removed from all the views, and the result isn’t very soothing.</p><p>Consider that only one view is visible at a time. Tapping an item in the current view will push a new view on top of the previous one, whereas tapping the “back” button in the navigation bar will reveal the previous one again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d0lq8oZrwqQHm5sacFqgOA.jpeg" /><figcaption>Example from <a href="https://apps.apple.com/us/app/belingual-language-learning/id1499647506#?platform=iphone">BeLingual</a></figcaption></figure><h3>Best Practices</h3><p>In the Navigation Bar, the user’s current position in the hierarchy can be displayed in the bar’s title. An escape button is always provided that can be either labeled “Back” or the name of the view the user was previously in accompanied by a chevron that looks similar to the “less than sign”. It should always be made clear for the user where he stands and where he can go — the navigation should be clear and intuitive. Avoid having too many views inside the hierarchy — organize the app in order of having the least amount of views, and the least amount of taps to reach the desired content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ul74HLWsZD_3gcZIhg4XMQ.jpeg" /></figure><p>Another navigation style that has been on iOS since the beginning is Modality. This is a great way to present content to the user that is not included in the main flow. They are contextual and usually do not provide any navigation inside, focusing only on one specific objective to be concluded. Apart from presenting tasks, the modals can also help by displaying important information.</p><p>Modality presentations:<br>• Action Sheets<br>• Sheet Modal View<br>• Activity Views<br>• Fullscreen Modal View<br>• Alerts</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2df6CXb9qoms4gzNNM73cg.jpeg" /><figcaption>Action Sheet / Sheet Modal View / Activity View / Fullscreen Modal View / Alert</figcaption></figure><h3>Best Practices</h3><p>Just like the Navigation Bar, the Modality should also have identifiable actions. The modal is presented outside of the user’s current flow, so the action to take must be clear. Choose a clear title that identifies what the modal is for, and always add an explicit exit button (Done and Close, at the right, or Cancel at the left since it’s a destructive action).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U8kpwIdj0mVv6JviK6sHqw.jpeg" /><figcaption>Example from <a href="https://apps.apple.com/us/app/translate-now-translator/id1348028646#?platform=iphone">Translate Now</a></figcaption></figure><p>Make use of this design technique wisely since taking the users out of their context is not the best option, unless it’s necessary. Provide this experience only when the user really needs to focus on making a decision that is outside of the current flow. Aside from using it only when necessary, they should also be very simple and clear. Letting the users navigate inside a modal experience can become confusing, since the path back might not be so clear. When going back, if there is content that needs to be saved, present an alert that helps the user choose whether he wants to keep it or lose it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HI95bSeIvoptnzCb7QTrgA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GxGvkaoJ9n8rtOKMC_qoAw.png" /></figure><p>A navigation bar is usually placed at the top of the view, below (1.) the Status Bar, and contains 3 main components: (2.) a left item, (3.) a title, and (4.) a right item(s) (both 2. and 4. are optional).</p><p>This bar provides hierarchical navigation between views, and is one of the ways to prevent the user from getting lost inside an app. The navigation bar can be paired with (5.) a Search Controller and (6.) a Scope Indicator.</p><h3><strong>1. Status Bar</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vsByPhXni4E4e5G8BRtuYw.jpeg" /></figure><p>The Status Bar displays contextual information about the device, and it appears on the upper edge of the view. The elements that are usually in use are the time, the cellular carrier, the wifi connection symbol, and the battery level, but this information is influenced according to the device.</p><p>When designing, avoid using a custom status bar, since the system one is recognizable for everyone, and it feels consistent throughout all apps. The Status Bar can toggle between two states, light and dark, so choose the one that is more readable depending on the background. This bar should be visible most of the time (avoid hiding it permanently) since the user has to exit the app to consult the information that is displayed there.</p><h3><strong>2. Left button</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AgK_R_U4wFmbjJCEhuZ1QA.jpeg" /></figure><p>This button is the easy path for the user to return to their previous location and it’s usually named after the view the user will go back to. It can also be named “Back”, but specifying the name of the previous view will make the path clearer.</p><h3><strong>3. Title</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wi81-4dMRReOQV48_VSAdg.jpeg" /></figure><p>The navigation bar’s title displays the current position of the user which provides a little bit more context about what is being presented. However, the title can be hidden if it feels redundant or highlighted by using the large style, according to the content of the view.</p><h3><strong>4. Right button</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZXVN6hK6xvvWsBUVkcvJnA.jpeg" /></figure><p>The buttons that are placed on the right, can assist in managing and affecting the whole view, and they can be comprised of label or symbol buttons. The symbol buttons are usually about editing, sharing or adding options, but although it’s possible, consider not crowding this space with a lot of controls, since the space is limited and the user might lose focus. The label buttons that are usually used are “Edit”, “Done”, “Cancel” or “Close” (in this case only one should be selected)</p><h3><strong>5. Background</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XlH7eAYKIzuV5a1JviSFJg.jpeg" /></figure><p>The default background of a navigation bar is a material (it is transparent and has a blur effect) and it shouldn’t be hidden, since it allows for the content to scroll seamlessly behind it. Disabling it is not advised since it will affect some accessibility options.</p><h3><strong>6. Search Controller</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jsz5g0SQyUVC3F-I_MbGNQ.jpeg" /></figure><p>A Search Controller allows users to perform a search that is influenced by the content typed and can be displayed alone or in a Navigation Bar. When used in a Navigation Bar, it can be pinned to it and accompany the scroll or it can be hidden and only accessed with a swipe down. The Clear Button should be enabled to facilitate the content being erased faster. The Cancel Button should also be enabled to exit the search anytime.</p><h3><strong>7. Scope Indicator</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IUnLsrbENNMqUBqtNt1-WQ.jpeg" /></figure><p>A Scope Indicator contains two or more segments that can be helpful to separate the different categories in which to search. The number of segments should be no more than 3, considering the adaptability to smaller devices. The content should be consistent, meaning that all the options should occupy almost the same width of the segment.</p><h3>Wrap up</h3><p>We hope this can help you learn and avoid some mistakes on your journey. Feel free to visit our Navigation Bar Figma library. A huge thank you to the other <a href="https://airapps.co/">Air Apps</a> team members who contributed to the Figma library, <a href="https://medium.com/u/df563e590dcd">Carmine Acierno</a> and <a href="https://medium.com/u/341c38ed18e9">Yugi Aragão</a>.</p><p>Leave us a comment if you have any questions. Or contact us at business@airapps.com</p><p>Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b22d107bace4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/airapps/ios-navigation-bar-design-guide-b22d107bace4">iOS Navigation Bar Design Guide</a> was originally published in <a href="https://medium.com/airapps">Air Apps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>