> ## Documentation Index
> Fetch the complete documentation index at: https://docs.doglytdc.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# DoglyTdc on mobile

> PWA access, the native experience, and device permissions.

## Overview

DoglyTdc offers a mobile experience through a PWA and a native application. The PWA is installed through your browser; the native app uses device features where available. The two experiences do not necessarily have the same permissions or integrations.

## Who it is for

* People accessing DoglyTdc on a phone.
* Users who want a home screen shortcut.
* People who need to understand notifications and app locking.

## How to open

**1. Choose your experience**

Check the installation area for your device. Installing the PWA is not the same as installing a native package.

**2. Install the PWA when available**

Use the installation option offered by your browser. On iOS, follow the Safari sharing instructions to add it to your home screen.

**3. Sign in**

Open the app and complete authentication. Follow the introduction and review the requested permissions.

## Screens and features

![Screenshot: Mobile](https://mintcdn.com/dogly-tdc/qOnot79kPtISSKbW/images/doglytdc/download.png?fit=max\&auto=format\&n=qOnot79kPtISSKbW\&q=85\&s=efd1a310cdbdc8c740283f0fd1e9132a)

Mobile in DoglyTdc

### PWA installation

The installation screen adapts its instructions to your browser and device. The automatic button depends on the browser making installation available. If that option is not ready, follow the manual instructions shown on screen.

### Native application

The installation center includes instructions for preparing the Android app. These instructions do not imply that a release is available in an app store. Native features depend on the platform and the components available in the app.

### Sign-in and introduction

The mobile experience checks your session before opening the dashboard. It may show an app lock, introduction, permissions, and a plans screen. The flow includes an option to continue after the plans presentation.

**1. Complete the introduction**

Go through the app's initial guidance.

**2. Review requests**

Only authorize access you intend to use.

**3. Open the dashboard**

Continue to the features available to your account.

### App lock

If app locking is enabled, the app asks you to unlock it before continuing. The flow supports a PIN or biometrics, depending on your settings. Biometric verification requires the native environment and an available biometric component.

## Credits and limits

Installing the PWA or native app does not grant unlimited credits. The mobile experience checks your subscription and may display plans. Installation does not replace the account's feature access requirements.

## Permissions

The permissions introduction includes notifications, microphone, storage, and phone access. Completing a step does not prove that the operating system granted every permission. Push requires the native environment, available components, and notification permission. Installing the PWA or accepting a browser prompt does not guarantee native push.

For calls and audio, your browser or device may request microphone access. Also review permissions in your system settings.

## Common errors

Quoted messages retain their Portuguese interface wording.

| Message or situation | What it means | What to do |
| - | - | - |
| Aguardando navegador… | Automatic installation is not available yet. | Follow the screen's manual instructions. |
| Sessão expirada. Faça login novamente. | The action requires a valid session. | Sign in again. |
| Notifications do not arrive | The environment or permission may prevent delivery. | Check which experience you use and review device permissions. |

Do not send your PIN, password, or private content when requesting help.

## Frequently asked questions

> [accordion] Are the PWA and native app the same installation?
>
> No. The PWA uses browser installation; the native app has its own environment.

> [accordion] Does installing the PWA guarantee push notifications?
>
> No. Native push requires the native environment, available components, and permission.

> [accordion] Do biometrics work in every browser?
>
> No. Biometric verification in this flow requires a compatible native environment.

## Related

> [card] [Notifications](https://docs.doglytdc.dev/en/doglytdc/account/notifications.md)

> [card] [Support](https://docs.doglytdc.dev/en/doglytdc/help/support.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.