FM BetterForms
BF Editorfmbetterforms.com
Engineering Reference Docs
Engineering Reference Docs
  • BF Streaming Proxy
  • Updating the Helper File
  • Connection Trouble Shooting Guide
  • Software Testing - Overview
    • Types of Testing
    • UX/UI Checklist
      • Pages
        • Login 🔑
        • Pricing 💵
        • 404 🤷‍♂️
        • Contact Us ☎️
        • Sign Up 👋
        • FAQ ❓
        • Blog Post 🗞
        • Careers 💼
        • Team 👫
        • Cart 🛒
        • Press 📸
        • Search results 🔍
      • Elements
        • Avatar 😁
        • Badge 📛
        • Button 🖲️
        • Card 🃏
        • Table 📏
        • Icon 🌠
        • Text Field ⌨️
        • Toggle 🎛️
        • Loading ⏳
        • Modal 🎉
        • Tooltip 🛠
        • Search 🕵️‍♀️
        • Navigation 🧭
        • Radio 📻
        • Checkbox ☑️
        • Tabs 🗂
        • Toast 🍞
      • Flows
        • Submitting a form 📨
        • Making a payment 💳
        • Contacting support 🆘
        • Deleting account 🗑
        • Tracking progress 📈
        • Resetting password 🤫
        • Showing input error 🚨
        • Entering a promo code 🏷️
        • Saving changes 💾
        • Canceling subscription 🛑
      • Topics
        • Responsiveness 🎚
        • Typography 🔤
        • Dark mode 🌑
        • Accessibility 🚹
        • Colors 🎨
        • UX Writing ✏️
      • Brand
        • Logo 💠
        • Social Media 🔉
        • Typography 🔠
    • FM BetterForms - Quality Assurance
    • JavaScript Libraries
  • Rollbacks and Version Control
  • BF Server Proxy
  • Base code End of Life - 0.8.78-0.8111
  • Setting up Auth0
    • Introduction
    • Getting started
      • Creating a tenant
      • Creating Application
      • Additional customizations
        • Allowed Callback URLs
    • Creating a Database
      • Choosing different login options
        • Social Connections
        • Username and password (Auth0)
        • Creating new BF Users
        • Using Auth0 in an iFrame
        • Configuring FM BetterForms
        • Additional Notes
  • Create an S3 Bucket on AWS
  • ApexCharts - Getting started
  • BF Enterprise Documentation
    • Overview
      • Features
      • Overview Diagram
    • Requirements
    • Env File
    • Setting up the Server
      • Installation
      • Loading image to a local repository
      • Starting server
      • Restarting Policies
      • Scaling up
    • Hardware Recommendations
    • FM Credentials - Helper file
    • How it works
      • Development
      • Downloading environment data
  • BetterForms Error Pages API
    • Introduction
    • Dynamic Error Page
    • Static Error Page
    • Custom error pages
    • Custom error handlers
    • Error Code List
  • BF Streaming API
  • Creating a PWA
    • Introduction
    • Getting Started
      • Making it installable
      • Browser Support
      • Sending Push Notifications
      • Sending a Push Notification from the API Endpoint
      • Adding DOM Header Insertion to be Available for Offline Use
Powered by GitBook
On this page

Was this helpful?

  1. Creating a PWA

Introduction

PWA (Progressive Web Applications) offer several advantages that make them a desirable choice for web apps:

  1. Cross-platform compatibility: PWA can run on multiple platforms, including desktops, laptops, and mobile devices, without the need to develop separate native apps for each platform.

  2. Installation: PWA can be installed directly from the browser, allowing users to access the app quickly from their home screen or app drawer without going through an app store.

  3. Offline support: PWA can work offline or in poor network conditions by utilizing service workers and caching mechanisms. This ensures that users can still access and interact with the app even without an internet connection.

  4. Push notifications: PWA can send push notifications to users, enabling real-time engagement and communication. This feature allows businesses to deliver important updates, promotions, or personalized messages to their users.

  5. Improved user experience: PWA leverages web platform features to provide a seamless and engaging user experience. They can offer smooth animations, fast loading times, and a responsive design that adapts to different devices and screen sizes.

  6. Cost-effective development: Developing a PWA can be more cost-effective compared to building separate native apps for different platforms. With a single codebase, developers can reach a broader audience and maintain the app more efficiently.

By choosing a PWA approach, businesses and developers can provide their users with a native-like experience, increase user engagement, and reach a wider audience across various devices and platforms.

The following sections will explain how to transform your BF App into a PWA.

PreviousCreating a PWANextGetting Started

Last updated 10 months ago

Was this helpful?