UX | 10 Examples of Good User Experience (UX)

10 Examples of Good User Experience (UX)
trone | Undated (Summer 2021 or before)

Websites & Apps that Understand Humans

  1. Rover: Using Reviews to Build Trust | https://www.rover.com
  2. Duolingo: Tearing Down Roadblocks | https://www.duolingo.com
  3. Paypal: Letting Simplicity Rule | (Mobile App)
  4. MailChimp: Humanizing Technology | https://mailchimp.com (Note: Intuit acquired MailChimp in Q4/2021, the current interface does not reflect the article, which predates the acquisition).
  5. Starbucks: Making it Personal | (Mobile App)
  6. Google: Loading Super Fast Since 1997 | https://www.google.com/
  7. Simple: Adding Clarity and Digestibility to Finance | (Mobile App)
  8. Nest Thermostat: Invisible Design | (Physical Product & Mobile App)
  9. Habitica: Using Gamification for Productivity | https://habitica.com/static/home
  10. Yelp: Everything Findable | https://www.yelp.com
  11. Bonus Example: From the Internet Archive (Poncho)

Author = Laura Flugga (trone)

URL = https://www.trone.com/blog/10-examples-good-user-experience-ux

Mobile Apps | Development Proposal Examples

Mobile Apps | 10+ Mobile App Development Proposal Examples in PDF
Examples.com | Undated

What Is a Mobile App Development Proposal?
A mobile app development proposal is a document that developers devise to promote their application. Through this proposal letter, they can request and negotiate a partnership or sponsorship. The purpose of this paper is to attract potential clients to purchase the mobile application. A business proposal is a complex document that involves a lot of necessary segments.

  1. Mobile App Development Strategies Proposal
  2. Mobile App Proposal Template
  3. Mobile App Pre-Development Proposal
  4. Mobile Application Developer Proposal
  5. Android Mobile App Development Proposal
  6. Mobile App Development Project Proposal
  7. Mobile App Development Form of Proposal
  8. Local Mobile App Request for Proposal
  9. Notice of Mobile App Request for Proposal
  10. Mobile App Development Partner Proposal
  11. Mobile App Financial Proposal

How to Construct an Impressive Mobile App Development Proposal

  1. Think Up a Gripping App Name
  2. Compose an Engrossing Cover Letter
  3. Structure Your Proposal
  4. Include a Cost Management Plan

What are the things to do before starting to develop a mobile app?
What are the elements of a business proposal?
What should be in the cover letter of a project proposal?

Author = Examples.com

URL = https://www.examples.com/business/proposal/mobile-app-development-proposal.html

Tool | BuildFire (Mobile App Dev)

Mobile App Development Timeline: A Realistic Perspective
buildfire | undated

Note = The Most Powerful App Maker For iOS & Android
BuildFire’s powerful and easy to use mobile app builder makes it so you can create mobile apps for iOS & Android in a fraction of the time and cost.
Simple and intuitive app builder – No coding required
Build custom functionality with our developer SDK
Build for FREE for 14 days. No credit card required
URL = https://buildfire.com/

Author = Ian Blair (build fire)

URL = https://buildfire.com/mobile-app-development-timeline/

Mobile Apps | Onboarding, w/Examples

The 10 best user onboarding examples to learn from
Appcues | Undated (2019? 2020?)

Top 10 favorite user onboarding examples:

Slack: Educates users with empty states and a friendly bot
Duolingo: Leads with the product experience
Grammarly: Takes a “learn by doing” approach
Tumblr: Charms with personality and personalization
IBM’s Cognos Analytics: Delivers consumer-grade UX in an enterprise product
Avast: Gives value before you ask for buy-in
Toggle: Lets users learn at their own speed
Avo: Makes signup easy and worry-free
TikTok: Teaches users how to get even more value from the product
Reclaim: Introduces users to your way of thinking

The basics of great user onboarding
Onboarding is the process of acquainting a new user with a product
. A great user onboarding experience shortens your new users’ time to value, guides them to their aha moment, and gets them to activate faster.

8 great user onboarding UX and UI patterns
Throughout our extensive research into what makes for amazing onboarding, we’ve found that there are 8 onboarding UX and UI designs that commonly contribute to a better onboarding experience. These include:
A welcome message greets the user with a short, friendly message that acquaints them with the product.
Product tours explain the product features most important to each user.
Progress bars indicate how long the onboarding experience takes, so users know how long they’ll need to commit.
Checklists provide an explicit list of tasks for the user to complete.
Hotspots direct attention to certain product features without interrupting their workflow.
Action-driven tooltips are small pop-ups that provide advice when a user performs a specific action.
Deferred account creation drops the user right into the product without requiring the user to register.
Persona-based onboarding tailors the product experience based on the user’s responses to a short survey.

These onboarding experiences are not mutually exclusive—many products will include 2 or 3 of these patterns depending on what their users need. Consider these a toolbox of sorts. When designing your onboarding, see how you can introduce these 8 UX and UI patterns to improve the user experience. If some of them don’t have a place in your onboarding flow—don’t sweat it.

All onboarding experiences should follow 4 steps
These 4 steps of successful user onboarding are:
Drive users toward key actions: Understand what actions are most likely to drive activation in your product and then build your onboarding toward getting users to those points. For example, if data shows that users who sync their Google calendar with your product are more likely to renew after the first month, then prioritize syncing users’ calendars in onboarding.
Focus your product around onboarding first: Just because your onboarding has a goal in mind doesn’t mean it can skip everything else. Make sure you show users everything they need to know before you get to your key action.
Add new UI where it’s needed most: Find areas that might be confusing or difficult for new users and use UI patterns to make it easier. Maybe that’s a modal that describes a feature, a tooltip that explains a button’s function, or a hotspot that draws the eye of a user.
Analyze, adjust, and repeat: No onboarding experience is perfect, and even the best onboarding experiences continue to be experimented on and updated. Conduct user research and run A/B tests to find out how you can make your onboarding even more effective at improving product adoption.

10 onboarding examples are commented

Onboarding FAQs

What is user onboarding?
User onboarding is the process of educating users and showing them the value of your product.
The onboarding process starts the first time someone tries your product and ends when they either churn or become a regular user. For some products, this means onboarding will be a matter of minutes, while others might require days to get people to a point where they can comfortably use the product as intended.
The primary goal of onboarding is to teach users about your product, personalize the product for their needs, and lead them to their aha moment—the first time they see the benefits your product can bring.

Why is user onboarding important?
User onboarding is important because it helps ease users into a new product. It’s a chance for them to be shown how it works, so they don’t have to waste time figuring it out on their own.
User onboarding is also crucial for companies. A good introduction of your product improves the overall user experience as users are introduced to product features and how to use them. When the onboarding is successful, it directly impacts customer retention, one of the most important profit metrics. If you improve retention by only 15% in the first week, that could boost revenue by 40% as each succeeding week’s cohort staves off churn that much longer. Great onboarding is how you achieve this.

How do you design a good onboarding experience?
A good onboarding experience is created when:
New users are given the tools and knowledge to be successful.
The onboarding experience is purposefully designed to guide users toward a key action that promotes activation.
Onboarding experiences are personalized based on segmentation.
UX and UI design is informed by user feedback and data to create an easy and intuitive process.
You invest in tools that make it easier to give users the experience they’ve come to expect.

If you do all 5 of these things well, then your onboarding is on the way to improving overall product adoption and reducing churn.

Author = Jackson Noel (Appcues)

URL = https://www.appcues.com/blog/the-5-best-user-onboarding-experiences

Mobile Apps | Case Studies (Peerbits)

peerbits App Case Studies
peerbits | Undated

Real-time tracking app, real-time tracking and remote diagnostics
URL = https://www.peerbits.com/case-studies/real-time-tracking-solution.html

Social networking iOS app, connect with new people
URL = https://www.peerbits.com/case-studies/social-networking-app-for-iphone.html

Petrol filling station app, the official app for the largest chain of filling stations in Oman
URL = https://www.peerbits.com/case-studies/petrol-filling-station-management-app.html

ATM food solution, an IoT-controlled automated marketplace
URL = https://www.peerbits.com/case-studies/atm-food-solution.html

Marketplace app, GetItDone
URL = https://www.peerbits.com/case-studies/getitdone.html

URL = https://www.peerbits.com/case-studies/m2r.html

Fishency, building a better way to fish like a pro
URL = https://www.peerbits.com/case-studies/fishency.html

URL = https://www.peerbits.com/case-studies/jewlot.html

Nurse Alert, a cohesive solution to nursing activity
URL = ttps://www.peerbits.com/case-studies/nurse-alert.html

Apply, a tinder-like job search app
URL = https://www.peerbits.com/case-studies/apply.html

Photograff, Graffiti
URL = https://www.peerbits.com/case-studies/photograff.html

URL = https://www.peerbits.com/case-studies/repd.html

Epic Delivery
URL= https://www.peerbits.com/case-studies/epic-delivery.html

Throne, the eCommerce Marketplace App
URL = https://www.peerbits.com/case-studies/throne.html

URL = https://www.peerbits.com/case-studies/seatsplanet-travel-app.html

BusMaps, plan bus trip with navigation travel app
URL = https://www.peerbits.com/case-studies/busmaps-navigation-app.html

URL = https://www.peerbits.com/case-studies/tapnsell.html

Loyal Books

Frimb, Food & Drink app that connects socially and share recipes globally with food lovers
URL = https://www.peerbits.com/case-studies/frimb-food-drink-app.html

Fashion Sizzle, capture and share the clothing trends with fashion lovers on FashionSizzle. success story
URL = https://www.peerbits.com/case-studies/fashion-sizzle-photo-app.html

Peerbits Works
URL = https://www.peerbits.com/works.html

Author = peerbits

URL = https://www.peerbits.com/case-studies.html

Mobile Apps | Terms & Conditions

Mobile App Terms and Conditions Template
Termly Legal Team | Nov 13, 2020

Table of Contents
What Are Mobile App Terms and Conditions?
Are Terms and Conditions for My Mobile App Required?
App Store Terms and Conditions Requirements
Common Clauses to Include in Your App Terms and Conditions
Terms and Conditions By App Type
Getting User Agreement to Your App Terms and Conditions
Mobile App Terms and Conditions Samples
How to Write Terms and Conditions for Mobile Apps
Free Mobile App Terms and Conditions Template
App Terms and Conditions FAQs

Author = Termly Legal Team

URL = https://termly.io/resources/templates/app-terms-and-conditions/

Mobile Apps | Requirements

Functional and Non-Functional Requirements for Mobile App: What’s the Difference?
Lvivity Team | February 20, 2021

Functional requirements for mobile applications describe what specifically needs to be implemented in a particular system or product and what actions users have to take to interact with the software. They determine what the system should do.

Non-functional requirements for mobile app show what properties and features a particular solution has, namely, how the system will work and why.

What do Functional Requirements Include?
We can highlight three main groups of functional requirements:
Business requirements. These define the high-level goals set by the customer’s company that is ordering the software development and stipulate what the system is to solve in terms of their business. Example: an application allowing potential customers to browse through the company’s product catalog and to purchase products.
User requirements. These describe the system goals/objectives the users may reach when using the created system (UseCases). Simply put, this is what a user can do: sign up, view certain content, recalculate data using a specific algorithm, and other functions.
Functional requirements. These define a list of actions the system has to perform. In addition, they have to specify how the system responds to various input data, how it behaves in particular situations, and so on.
This group also includes system requirements describing hardware and software environment features necessary for correct operation.

Non-Functional Requirements in Simple Words

As a rule, the non-functional requirements primarily include various product quality attributes determining system quality features, most often as examples below:
Availability – requirements for app continuous running, for example, 24/7, minimum idle time, etc.
Reliability – app behavior in case of alarm status, for example, automatic restart and operation recovery.
Scalability – ways to expand the system and avoid adversely affected performance.
Performance – how many simultaneous users or transactions the system is to service and its response time.
Security – app operation and use of safety requirements related to access control, private data processing, and external attack risk reduction.
Usability – ease of use and user-friendly interface, that allow users to seamlessly interact with the product.
Extensibility – requirements for app extensibility in case there is a need to add new functional requirements.

Wikipedia = Non-functional requirement
URL = https://en.wikipedia.org/wiki/Non-functional_requirement


Author = Lvivity Team

URL = https://lvivity.com/functional-and-non-functional-requirements

Tool | Storybook Native

Storybook for Mobile Applications
Medium| Feb 25, 2021

Announcement = official release of Storybook Native, a new tool for showcasing mobile applications and components.

Storybook = https://github.com/storybookjs/native#installation
Note: Before using this, ensure that you have installed NodeJS
NodeJS = https://nodejs.org/en/download/

Examples of how to use this module as both a build tool and as a component library can be found in the examples folder. The app folder inside each example contains the source code of the application the example is for.

Android storybook with controls
Flutter storybook with controls
Cross platform storybook
iOS storybook with deep linking

Author = Adil Malik

URL = https://medium.com/storybookjs/storybook-for-mobile-applications-97e3a229fb3c