Contact person: Business Client

Phone:Show

Email:Show

Location: Kampala, Uganda

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"The objective is to create a fully offline file-sharing application that forms an ad-hoc, multi-hop mesh network and runs natively on both Android and iOS. Devices should discover one another automatically, relay files even when they are not in direct range, and keep transfers alive as phones move through the topology. No internet connection, central server, or cellular data may be required at any point; every packet must flow peer-to-peer until it reaches its destination.

Core scope
• Build separate native clients (Kotlin/Java for Android, Swift/SwiftUI for iOS) or use a cross-platform framework if it can still leverage each OS’s low-level mesh APIs (Wi-Fi Aware, Wi-Fi Direct, Bluetooth LE, Multipeer Connectivity, etc.).
• Implement routing that supports at least three hops in practical tests, automatically re-routing around dropped nodes.
• Transfer any standard file type while maintaining original metadata and folder structure where applicable.
• Background-mode operation on both platforms so users can continue sharing while the app is minimized.
• Basic safety measures—permission handling, file size limits, and graceful interruption recovery—must be in place.
• Deliver clean, well-commented source code, build/run scripts, architectural documentation, and a short test video that proves two out-of-range handsets can exchange a file through a third relay device.

What I’d like from you
Submit a detailed project proposal outlining your suggested technology stack, multi-hop routing strategy, timeline, and milestones. Highlight prior experience with mesh networking, low-level connectivity, or offline communication apps where relevant.

Acceptance criteria
1. A reproducible build for both OSs that installs from TestFlight / APK and functions without the internet.
2. Demonstration of a three-device, two-hop file transfer in under one minute for a 5 MB file.
3. Source code, documentation, and a high-level architecture diagram handed over at project close." (client-provided description)