Download the PHP package pushinbr/pam-native-nfc without Composer
On this page you can find all versions of the php package pushinbr/pam-native-nfc. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download pushinbr/pam-native-nfc
More information about pushinbr/pam-native-nfc
Files in pushinbr/pam-native-nfc
Package pam-native-nfc
Short Description Lifecycle-safe NDEF reading and writing for PAM Native on Android and iOS.
License Apache-2.0
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package pam-native-nfc
Why PAM Native NFC
Run bounded NFC sessions, parse typed records, and handle platform capability differences without leaking native session objects. The public API is strictly typed for PHP 8.5; expensive or frame-sensitive work stays in Rust or the platform SDK instead of crossing the application boundary every frame.
| Best for | A focused capability you can add to any PAM Native application |
| Native path | Android NFC · Core NFC |
| Application model | Composer package + generated native integration |
| Design rule | Independent module; no feed, vertical, or application template bundled |
What you can build
- Asset and inventory tagging
- Contactless onboarding and pairing
- Smart posters, tickets, and physical experiences
Quick start
Already have a PAM Native project? Add only this capability:
New to PAM? Follow the five-minute PAM Native setup once, then return here. Your application stays a normal Composer project with a committed lockfile.
See it in action
Read and write NDEF tags from PAM Native with one lifecycle-safe API on Android and iOS.
Only one NFC session may be active at a time. iOS presents the system NFC sheet and requires the NFC capability in the signing profile. Android uses reader mode and requires a foreground Activity. The queue is bounded to 128 events. NDEF payloads are limited to 1 MiB in PHP before reaching native code; the physical tag's capacity is checked at write time.
What installation does
pam add nfc resolves the official compatible package, performs a non-mutating Composer preflight, updates the normal composer.json and composer.lock, refreshes generated native integration when required, and leaves the project ready for pam doctor validation.
Use pam packages to inspect availability and pam remove nfc to uninstall the capability safely. Direct Composer commands are an advanced interoperability path; PAM is the supported application workflow.
API guide
| API | Responsibility |
|---|---|
Nfc |
Begin reading, write NDEF, poll events, and end sessions. |
NdefRecord |
Build URI, text, MIME, and external NDEF records. |
NfcEvent / NfcEventKind |
Consume typed tag and session events. |
NfcAvailability |
Inspect platform and hardware support. |
All coded states, kinds, and variants are sequential integer-backed enums. Use enum cases in application code; do not depend on raw wire numbers.
Production checklist
- End sessions when the owning screen leaves the foreground.
- Validate every record type, length, and payload before use.
- Treat tag data as untrusted external input.
- Run
pam doctor,pam test, and a signed release build on every supported platform. - Exercise denial, cancellation, backgrounding, process restart, and offline behavior before release.
Troubleshooting
- Session will not start: only one session may be active.
- iOS cannot scan: verify NFC entitlement and a compatible signed device.
- Write fails: compare the encoded payload with the physical tag capacity.
- Native integration is stale: run
pam doctor --fix, rebuild the native host, and inspect the first reported diagnostic.
Compatibility and support
This package targets PAM Native 0.8.x, Android API 26+, and iOS 15+ unless a platform-specific section above states a stricter requirement. Platform SDKs, credentials, entitlements, physical hardware, and store configuration remain application responsibilities.
Security vulnerabilities should be reported through the repository security policy or GitHub private vulnerability reporting, not a public issue.
