# Principles

The Principles provide an overarching rationale to the design of mobile apps and services that use IPFS. These principles cover the broad gamut of issues designers and developers might encounter. These are suggestions for designers and developers when building their apps and services.

Each starts with analysis taken from the [research](https://app.gitbook.com/@jkosem/s/ipfs-mobile-guidelines/user-research/interviews). This analysis serves as a basis for deeper considerations for designers and developers. Each principle in turn includes Do’s and Don’ts on how to make it happen and an illustration of what it could look like.

## Respect the device

Apps and services for mobile aren't reformatted desktop apps. They need to take into account a host of different issues, from battery life to signal.

[Read more](https://jkosem.gitbook.io/ipfs-mobile-guidelines/design/principles/respect-the-device)

## Explain, don't overwhelm

Stategically highlight the unique and key benefits like privacy and speed that other apps not on IPFS don't have. Avoid long, technical explanations in interfaces.

[Read more](https://jkosem.gitbook.io/ipfs-mobile-guidelines/design/principles/explain-dont-overwhelm)

## Make privacy work for the user

There is no shortage of concern about privacy and security for all levels of users. What users want is assurance that they have some level of privacy or security so their data and files are safe.

[Read more](https://jkosem.gitbook.io/ipfs-mobile-guidelines/design/principles/make-privacy-work-for-the-user)

## Give control over data

Mobile apps and services should help manage files. They can do this by respecting the needs users may have with availability, discoverability and persistence.

[Read more](https://jkosem.gitbook.io/ipfs-mobile-guidelines/design/principles/give-control-over-data)

## Be seamless

The user shouldn't necessarily know how they're connected, whether through wifi, bluetooth or otherwise. They should just feel confident that data is getting sent and received, not how.

[Read more](https://jkosem.gitbook.io/ipfs-mobile-guidelines/design/principles/be-seamless)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://jkosem.gitbook.io/ipfs-mobile-guidelines/design/principles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.