You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Magically Create and Transfer Content to NFC ePaper Badges**
7
+
8
+
The Magic ePaper app is an open-source Flutter application that lets users design and transfer content to a tri-color, battery-free NFC ePaper badge. The app features an intuitive UI with drawing tools, text input, emoji support, font customization, and image editing (rotation, brightness, contrast, filters optimized for ePaper such as Floyd–Steinberg and Atkinson dithers). It supports NFC-based reading/writing of images and advanced NDEF data (text, URLs, vCards, app launch). A built-in Image Library stores processed images for quick transfers. Additional tools include QR/barcode generation, employee ID, and price tag creation.
9
+
10
+
## Download
11
+
12
+
*[Latest Release Build](https://github.com/fossasia/magic-epaper-app/tree/app) in the app branch
13
+
14
+
## Permissions
15
+
***NFC**: For reading and writing data to the ePaper badge via NFC.
16
+
***Internet**: For network operations and updates.
17
+
18
+
## Translations
19
+
20
+
Translators can support the project on Weblate here: https://hosted.weblate.org/projects/fossasia/magic-epaper-app/
***main**: All development goes on in this branch. If you're making a contribution, you are supposed to make a pull request to _main_. PRs to main branch must pass a build check on CI/CD.
67
+
***app**: This branch contains the latest app builds and releases.
68
+
***version**: This branch stores the version information for the app builds (versionName and versionCode). This is used in our workflows for automatic versioning wherein the next version information is automatically fetched from this branch and used for building the app.
69
+
***fastlane-android**: This branch contains information and metadata used by fastlane to automate Android deployment.
70
+
***pr-screenshots**: This branch stores screenshots for every open pull request, which are shown in comments in every pull request.
71
+
72
+
## Contributions Best Practices
73
+
74
+
Please read FOSSASIA's [Best Practices](https://blog.fossasia.org/open-source-developer-guide-and-best-practices-at-fossasia/) before contributing. Please help us follow the best practice to make it easy for the reviewer as well as the contributor. We want to focus on the code quality more than on managing pull request ethics. Here are some basics:
75
+
76
+
* Single commit per pull request
77
+
* For writing commit messages please read the [CommitStyle.md](docs/commitStyle.md).
78
+
* Follow uniform design practices. The design language must be consistent throughout the app.
79
+
* The pull request will not get merged until and unless the commits are squashed. In case there are multiple commits on the PR, the commit author needs to squash them and not the maintainers cherrypicking and merging squashes.
80
+
* If the PR is related to any front end change, please attach relevant screenshots in the pull request description.
81
+
* Before you join development, please set up the project on your local machine, run it and go through the application completely. Press on any button you can find and see where it leads to. Explore.
82
+
* If you would like to work on an issue, drop in a comment at the issue. If it is already assigned to someone, but there is no sign of any work being done, please free to drop in a comment and start working on it.
83
+
84
+
## Dev Container usage
85
+
86
+
Opening this repository in VSCode, GitHub Codespaces or another supported editor/IDE will allow the repository to be opened in a [Dev Container](https://containers.dev/).
87
+
88
+
The Dev Container contains all necessary dependencies and tools required to build, run and debug flutter applications.
89
+
90
+
### How to connect via `adb`
91
+
92
+
:warning: In case `adb` is already installed and running on the host it may need to be stopped before continuing.
93
+
94
+
This Dev Container allows several different methods of connecting to a device via `adb`:
95
+
96
+
#### Entirely from inside the container (USB pass-through)
97
+
98
+
:information_source:**Windows** and **MacOS** need a working **USB/IP** setup. Read more in the official [Docker Desktop documentation](https://docs.docker.com/desktop/features/usbip/) and in this [blog post](https://blog.golioth.io/usb-docker-windows-macos/).
99
+
100
+
The Dev Container bind-mounts `/dev/bus/usb/` and sets the correct access controls for a seamless integration. \
101
+
Enable [USB debugging](https://developer.android.com/tools/adb#Enabling) on your phone and try to find it via:
102
+
103
+
```bash
104
+
adb devices
105
+
```
106
+
If it shows up, everything is ready and you can run `flutter run` to push a development version of the app onto your device.
107
+
108
+
#### Using the host's `adb` server
109
+
110
+
If `adb` is already installed on the host, the tools in the Dev Container can be configured to use the host's `adb` server:
111
+
112
+
1. Ensure the `adb` server is listening on **all interfaces**
113
+
1. If that is not the case, kill and restart it: `adb kill-server && adb -a server` (the `-a` instructs it to listen on all interfaces).
114
+
1. Set or export the following environment variable before executing `adb` or `flutter run`: `ADB_SERVER_SOCKET=tcp:host.docker.internal:5037`
115
+
1. You should now be able to list the devices connected via USB to the host
116
+
117
+
#### Wireless connection
118
+
119
+
Android 11 and higher support wireless debugging. Check out the [documentation](https://developer.android.com/tools/adb#wireless-android11-command-line) for more information. \
120
+
For this mode it is required that both the workstation and the device are on the **same network**.
121
+
122
+
:information_source: This also works when developing inside **GitHub Codespaces**. In that case you can bring your device and the Codespace onto the same network by installing WireGuard, Tailscale or another overlay/mesh network on both the Codespace and your device.
123
+
124
+
Enable Wireless debugging as per the [documentation](https://developer.android.com/tools/adb#wireless-android11-command-line), then **pair**`adb pair <IP>:<PORT>` and **connect**`adb connect <IP>:<PORT>` and you should be able to find your device via `adb devices`.
4
125
5
126
## Table of Contents
6
127
-[Getting Started](#getting-started)
@@ -12,7 +133,6 @@ A new Flutter project.
12
133
-[Install Dependencies](#install-dependencies)
13
134
-[Running the Project](#running-the-project)
14
135
15
-
16
136
## Getting Started
17
137
18
138
This project is a starting point for a Flutter application that follows the
@@ -55,7 +175,6 @@ Android Studio or VS Code: Recommended IDEs for Flutter development.
55
175
56
176
Android Emulator or Physical Device: For running the application.
0 commit comments