aljaz/pear-docs
1
0
Fork 0
mirror of https://github.com/aljazceru/pear-docs.git synced 2025-12-17 14:34:19 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
0d7fbfe0c33c55e8ae7985651bc8dec3739f30f6
pear-docs/examples/bare-on-mobile.md
Sean Zellmer 5800a7031f Add Mobile Application Guide (#167) 
* Add "Making a Bare Mobile App" guide

* Change title to be 'Application' instead of 'App' in mobile guide

* Pin `autopass` to `1.x.x` in mobile guide

* Update "Bare on Mobile" to point readers to the mobile guide

* Add Bare mobile application guide to README.md

* Tweak wording in "Bare on Mobile"

* Remove "Cross-platform Pear App" example

This example app has been archived and is now outdated.

* Add missing link in SUMMARY.md for mobile guide

* Update mobile app guide to use new worklet api & support autopass@2.1
2025-03-18 08:54:42 +01:00

1.4 KiB
Raw Blame History

Bare on Mobile

Bare can be embedded into mobile applications to serve as the "Pear-end" where the peer-to-peer code of the application is run.

To get started with Bare mobile development via Expo, check out the "Making a Bare Mobile Application" guide. It uses the Bare on Expo template to build a mobile app for syncing passwords with the Pearpass desktop example. This example integrates Bare as an isolated thread, called a worklet1 , via react-native-bare-kit. All code passed when starting the worklet will run in the Bare runtime and can be communicated with via an inter-process communication (IPC) stream.

For deeper integration with a mobile application, the following examples can be used as references:

The Bare JavaScript runtime runs equally well on both mobile and desktop applications.

For further reference on using Bare, please refer to GitHub (Bare).

  1. This term was chosen to avoid ambiguity with worker threads as implemented by https://github.com/holepunchto/bare-worker. ↩︎