RU LINK: Smart NFC & QR Identity App, Launched and Updated on Both Stores

What the app does

• Profiles for every use. Personal, business and event profiles with a photo, contact details, social platforms and custom links, reordered and switched on or off individually, with a live preview of what people will see.
• Direct mode. A switch on the profile changes what a tap opens: the full profile, or one chosen link.
• Device management. Each card, stand or T-shirt shows up under Devices with its ID. Owners activate new ones, switch them on or off, mark one as lost, or buy more from the app.
• Share by NFC or QR. Tap a RU LINK product or show a QR code linked to a short rulink/username address. Images and files can be attached for NFC sharing.
• Connections. People, contacts, groups and connection requests, with search by name or company and discovery of RU LINK users nearby.
• Quick sign-in and notifications. Sign in with Apple or Google, plus push notification preferences the user controls.

Overseeing development

• Turned the client's product range into a scope and milestones for the Flutter build, so profiles, device linking, connections and sharing could be checked and signed off one at a time.
• Reviewed builds against that scope, with most attention on the flows the business depends on: activating a product, linking it to the right profile, Direct mode and lost-device handling.
• Kept the app, the custom API and admin panel, and the product catalogue consistent, so every product the client sells is something the app can activate and manage.
• Checked store-review requirements during development rather than at submission, such as offering Sign in with Apple alongside Google sign-in.

Store listings, launch and updates

• Prepared the App Store and Google Play listings: name and subtitle ("Stay Linked. Stay Ahead"), description, category (Productivity), age rating and the privacy policy link.
• Took version 1.0 through review to launch in October 2025.
• Managed the release cycle since then: five updates through 1.0.5 in August 2026, each one through review on both stores.

• Flutter for both platforms. One codebase keeps product activation, sharing and connections the same on iPhone and Android, and lets one team ship both store builds.
• The client's own API and admin panel. Profiles, products and orders live on infrastructure RU LINK controls, which suits a business that sells hardware and takes custom orders. The cost is more backend to build and run.
• Products are managed, not just linked. Devices can be switched off or marked as lost from the app, so a lost card doesn't keep sharing someone's details.
• QR next to NFC. T-shirts and stands rely on QR codes, and not every phone reads NFC, so every product works with a scan as well as a tap.
• Small, frequent updates. Five releases in ten months, each a small change, instead of one big redesign. That's less risk for customers whose products are already out there.

• Live on the App Store (iPhone, iOS 15.5+, also runs on Apple Silicon Macs and Apple Vision Pro) and Google Play.
• Six releases so far, from 1.0 in October 2025 to 1.0.5 in August 2026.
• Free to download and rated 4+. One app manages every RU LINK product, from cards to T-shirts to Google Review stands.

When an app is the control centre for physical products, launching it is only the start. Every card or stand a customer owns depends on it working after each update. RU LINK is that longer job: keeping the build tied to the product range, and shipping it through store review again and again without breaking what people already have.