Development in Flutter. I need RevenueCat implementation in my Android app ASAP. Products are created in the Play Store, I just need someone to input RevenueCat code and ensure the products are working and user receipts are sent to my server, and back to Google, properly. Will need RevenueCat added to Apple app and web app in the near future, but Android is the immediate priority at this moment. Futher work will be added after Android app has RevenueCat implemented and working.

I am seeking a skilled freelancer to create an App for me. The ideal candidate should have experience in web development and design, with the ability to work independently. The project involves creating a visually appealing and functional App without requiring coding skills from me. The freelancer should be able to handle all aspects of the App creation process, ensuring a smooth and efficient delivery.

Firstly, I want to state that I am not a coder. At all. The code I'd like you to review was entirely "vibe coded" using Antigravity and Claude. I don't intend to create a complete product using this method, in fact, I'd like to use real people as much as possible for my business. I used AI during this phase simply to see my ideas made material. I understand that this means the code itself is likely compromised in all sorts of ways, but I'm hoping that you can help me with that. Please speak with me as you would a fifth grader about the technical aspects of the code, assuming you'd like to work together from this point forward. My app is a free-to-user dating and date planning app that connects people through locally owned businesses. It serves two audiences: - **Singles** looking to meet and go on dates with other singles in their area - **Couples** looking for date night inspiration through a linked accounts mode

I am looking for a product developer to build the MVP for a new platform in the senior care space. The product concept and user journey are defined, and we need someone who can bring this vision to life. The ideal candidate will have experience in building MVPs, particularly in the senior care industry, and be able to complete the first phase of the project by the given deadline. Communication is also vital.

I am the founder of an existing consumer mobile app and am looking for an experienced senior engineer to tutor me on my own application’s architecture. The ideal candidate will have a strong background in mobile app development and be able to provide guidance on improving the app's structure and performance.

Title: iOS developer — integrate TSL 3138 UHF RFID reader (Bluetooth SDK) into existing app Type: Fixed-scope contract (small, well-defined first project — potential for ongoing work) Overview: We have a working iOS app prototype for a moving-industry operations system. We need a developer to integrate a TSL 3138 Bluetooth UHF RFID handheld reader so the app can scan RFID tags and drive a proximity-based "find" feature. This is a self-contained first engagement; strong work leads to a larger ongoing backend build. Scope of this contract: Pair the app with the TSL 3138 over Bluetooth (connect, disconnect, reconnect, battery/status). Inventory read: trigger a scan and receive the list of tag IDs (EPCs) in range. Reconciliation: compare scanned tag IDs against an expected list and flag which are missing. Hunt / proximity mode: stream each target tag's signal strength (RSSI) and expose it so the app can produce a "hotter/colder" cue as the operator approaches — tuned so a tag only confirms at close range (~1–4 ft), not across a room. (Achieved by adjusting reader transmit power and an RSSI threshold.) TSL's RFID Tag Finder demo app implements this behavior and is a useful reference. Read a QR code via the reader's built-in 2D imager (and/or device camera) as a fallback tag-ID input. Required skills: Native iOS development (Swift). Experience integrating a Bluetooth hardware SDK — RFID, barcode scanner, or similar peripheral. (Please describe a past project where you connected an app to a physical Bluetooth device.) Comfort reading a manufacturer's hardware SDK/documentation. Nice to have: Prior RFID/RAIN/UHF experience. Full-stack ability (Node/backend, databases) for potential ongoing work. We provide: The existing app prototype (demonstrates the full workflow and UI). A written spec defining the read, reconciliation, and hunt-mode behavior. The TSL 3138 reader hardware and TSL's iOS SDK (including the RFID Tag Finder demo). Deliverable: working reader integration demonstrated on our physical TSL 3138 + iPad, with the scan behaviors above functioning against real tags. Source code delivered and documented. To apply: briefly describe a Bluetooth-hardware integration you've shipped, and note any RFID experience.

We are seeking a skilled freelancer to update our existing phone application. The ideal candidate will have experience in mobile app development, particularly with Android and iOS platforms. The task involves re-skin of app's GUI, removing some features, and ensuring it is compatible with the latest operating systems. Attention to detail and the ability to deliver high-quality results are essential.

Join our team to develop a social travel app, Kite, using React Native (Expo), Node.js, TypeScript, and PostgreSQL. You'll work on both mobile and backend development, enhancing user experience and implementing new features. Collaborate with our team to ensure seamless integration and high-quality delivery. This is a part-time, ongoing project with a focus on innovation and user engagement.

1. What we need Primary scope: Google Play compliance. Bring our Android app to target API level 36 and keep it shippable. Secondary scope: web application updates. We may also want this developer handling updates to the bytrellus.com web application, including making sure those updates work correctly inside the Capacitor mobile app. We'll scope the specifics separately. We're looking to outsource ongoing work on this hybrid setup. It isn't a one-off engagement. We want a freelancer or independent consultant who stays on the project. 2. Current architecture Layer-Current state Web app-bytrellus.com, Next.js Mobile-Capacitor.js hybrid, iOS and Android, wrapping the web app Android listing-"Trellus: Local Delivered" Payments-Stripe, on-page iframe for card entry, saved cards on file Current target API-Below requirement, flagged by Google Play A few things you should know up front: • The Capacitor implementation used workarounds to make the hybrid approach function. • Portions of the HTML render conditionally based on detecting the Capacitor environment. • Cookies don't work in the native WebView. User and location state is carried by a session identifier passed as a URL parameter instead. • The native layer is undocumented. All of this works today and we're happy with it. We're being upfront so you can protect it through the upgrade. We're not looking for someone to rebuild it. 3. Primary scope in detail Core work: • Upgrade Capacitor to version 8, which is what targets API 36 • Toolchain: minSdk 24, compileSdk 36, targetSdk 36, Android Gradle Plugin 8.13.0, Java 21, Android Studio Otter or newer, plus the Gradle property-assignment syntax changes throughout • Audit and upgrade every Capacitor plugin for API 36 compatibility. Community plugins are where we expect breakage. • Handle the Android 16 behavior changes that affect us, including orientation-lock changes on large screens • Confirm the environment-conditional rendering behaves identically after the WebView upgrade • Confirm the URL-parameter session mechanism survives navigation, redirects, background resume, and checkout • Regression test the full shopping and checkout flow on real devices, both platforms. Emulator alone won't cover it. • Ship to Play and confirm acceptance • Check iOS SDK requirements while you're in there. Capacitor 8 changes both platforms, and Apple runs its own rolling minimum. Preserve the existing architecture What we need is confidence that the existing workarounds still function after the upgrade. Please don't replace them. • Confirm the session identifier propagates correctly through navigation, redirects, and the full checkout flow • Confirm environment-conditional rendering behaves identically post-upgrade • If something breaks, we want the smallest fix that restores current behavior rather than an improvement Not applicable: the app has no sharing functionality and no deep linking configured, so Android app link verification is out of scope. There are also no push notifications. Payment flow: checkout doesn't redirect to a payment provider's page. Card entry uses a Stripe iframe on-page, with saved cards on file through Stripe. Given no sharing, no deep links, and no push, the Stripe 3DS challenge is the only path where control can leave the page mid-session. That said, if you think something here is genuinely unsafe rather than just unfashionable, tell us. We'll listen. Out of scope • Rewriting the app as fully native • Redesigning the shopping experience • Migrating off Capacitor • Replacing the session-in-URL mechanism • Reworking the environment-conditional rendering Items to confirm at the start • Whether release capability covers both stores or Android only. Apple's certificate and provisioning chain is separate and expires on its own schedule. • Apple Developer account access, certificates, and provisioning profile status • Play App Signing enrollment status • Whether the build succeeds on the tooling Capacitor 8 requires: Android Studio Otter, Java 21, AGP 8.13 4. Secondary scope: web platform work We'd like to outsource ongoing development of the bytrellus.com Next.js application alongside the mobile layer, treating the two as one hybrid system instead of separate projects. Here's our thinking on keeping them together. Any change to the web app renders inside the mobile app, so web changes have to be validated inside the WebView on both platforms rather than only in a desktop browser, and they can't disturb the session-parameter mechanism or the environment-conditional rendering. If we split this across two people, that seam falls in the gap between them. We'll scope specific web updates separately. 5. Documentation We're after a long-term working relationship here, so this isn't about preparing a handoff to our internal team. We do still want two things written down: • A build-and-release runbook covering both platforms • A written inventory of the workarounds in the hybrid setup, what each one does, and why it exists

I'd like to build a social media app for pay it forward campaigns