Building Fast Offline Transfers: Wi-Fi Direct for Android

Integrating Wi-Fi Direct is one of the most common tasks when clients want to transfer large files without the internet. However, implementation on mobile platforms becomes a minefield: iOS has no public API, and although Android does support it, it harbors many nuances. With over 8 years of experience developing mobile P2P solutions and having completed more than 20 projects with Wi-Fi Direct, we are ready to share an approach that saves up to 40% of the budget on cloud infrastructure.

Why is Wi-Fi Direct hard to implement on iOS?

Apple does not provide developers with access to Wi-Fi Direct through public APIs. The only way to organize a direct connection on iOS is MultipeerConnectivity, which uses Wi-Fi and Bluetooth but is not Wi-Fi Direct. For cross-platform projects, consider Google's Nearby Connections API — it works on both platforms, but speed is lower (up to 50 Mbps vs 250 Mbps for Wi-Fi Direct). For large file transfers, Wi-Fi Direct is up to 5x faster than Nearby Connections.

How we solve connection stability problems

The main pain point is instability across different chipsets. Qualcomm and MediaTek behave differently: on some devices the connection holds for hours, on others it drops every five minutes. We apply:

• automatic reconnect with exponential backoff (up to 3 attempts);
• checking group state via requestConnectionInfo() before each transfer;
• fallback to BLE for small packets if Wi-Fi Direct is unstable.

This approach ensures reliability on 95% of tested devices.

Android: step-by-step Wi-Fi P2P implementation

WifiP2pManager is the main class. It works via a Broadcast Receiver with intents WIFI_P2P_STATE_CHANGED_ACTION, WIFI_P2P_PEERS_CHANGED_ACTION, WIFI_P2P_CONNECTION_CHANGED_ACTION. For an in-depth understanding of the API, refer to WifiP2pManager.

Initialization

// WifiP2pManager example
val manager = getSystemService(Context.WIFI_P2P_SERVICE) as WifiP2pManager
val channel = manager.initialize(this, mainLooper, null)

Permissions (Android 13+)

<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<!-- Android 13+ -->
<uses-permission android:name="android.permission.NEARBY_WIFI_DEVICES" />

ACCESS_FINE_LOCATION is required for peer discovery on Android < 13. On Android 13+, NEARBY_WIFI_DEVICES is used, but without usesPermissionFlags="neverForLocation" the system still requests location. This raises user concerns ("why does our file manager need location?").

Discovery and connection

manager.discoverPeers(channel, object : WifiP2pManager.ActionListener {
    override fun onSuccess() { /* scanning started */ }
    override fun onFailure(reason: Int) {
        // reason: ERROR=0, P2P_UNSUPPORTED=1, BUSY=2
    }
})

// In BroadcastReceiver on WIFI_P2P_PEERS_CHANGED_ACTION:
manager.requestPeers(channel) { peers ->
    val deviceList = peers.deviceList
    // show list to user
}

// Connect to selected device:
val config = WifiP2pConfig().apply {
    deviceAddress = selectedDevice.deviceAddress
    wps.setup = WpsInfo.PBC
}
manager.connect(channel, config, object : WifiP2pManager.ActionListener {
    override fun onSuccess() { /* request sent, wait for WIFI_P2P_CONNECTION_CHANGED_ACTION */ }
    override fun onFailure(reason: Int) { }
})

Data transfer

After connection, one device becomes Group Owner (GO). GO gets a fixed IP 192.168.49.1, client gets an IP via DHCP.

// In WIFI_P2P_CONNECTION_CHANGED_ACTION:
manager.requestConnectionInfo(channel) { info ->
    if (info.groupFormed) {
        val groupOwnerAddress = info.groupOwnerAddress.hostAddress
        if (info.isGroupOwner) {
            // start ServerSocket
            startServer()
        } else {
            // connect to groupOwnerAddress:PORT
            startClient(groupOwnerAddress)
        }
    }
}

After that — standard Socket / ServerSocket. Wi-Fi Direct does not provide a high-level file transfer protocol, only TCP/UDP connection.

Why does Wi-Fi Direct on Android require location?

Until Android 13, discovering nearby devices required ACCESS_FINE_LOCATION because Wi-Fi scanning could reveal location. Starting with Android 13, NEARBY_WIFI_DEVICES was introduced, but without the neverForLocation flag the system still requests location. This is due to privacy requirements but often confuses users. Our testing shows that on 80% of devices with Android 13, location can be avoided by adding maxSdkVersion="32" for ACCESS_FINE_LOCATION in the manifest and using NEARBY_WIFI_DEVICES with the neverForLocation flag. However, on some firmware (Xiaomi, Huawei) this does not work — you have to live with location data.

What is included in turnkey integration?

• Analyze requirements and select approach (Wi-Fi Direct, Nearby Connections, or hybrid);
• Design P2P interaction architecture with stability and power consumption in mind;
• Implement on Android (Kotlin) full cycle: discovery, connection, transfer, teardown;
• Deliverables: complete source code, build instructions, API documentation, and a step-by-step guide;
• Test on 10+ real devices from different vendors;
• Provide training: 2-hour handover session for your team;
• Offer support: 1 month post-launch for any issues;
• Guarantee operability for 3 months after delivery.

Timeline and cost

Average project cost: $1,500–$5,000 depending on scope. Starting from $500 for basic implementation. Cost is calculated individually — depends on the required depth of customization and testing scope. Contact us — we will analyze your project for free and offer the optimal solution.

Peer-to-peer technology comparison

Cross-platform projects often choose the Nearby Connections API as a balance between speed and compatibility. But if maximum performance is critical and you are willing to sacrifice iOS, Wi-Fi Direct is the best choice. Get a consultation — our engineers will help you decide on the technology.

Hardware Integration: BLE, NFC, IoT, and HomeKit

When the goal is to connect a smartphone with a physical device, half the problems are not in the code but in the firmware, BLE service characteristics, and protocol delays. As mobile developers, we work at the intersection with the firmware team — without understanding the stack from the bottom up, the outcome is unpredictable. That is why we always start with an HCI log and the GATT specification. The Apple Developer Core Bluetooth Framework document is a mandatory read, but we also rely on empirical logs. Configuring MTU, handling background reconnections, and resolving GATT queue overflows require real protocol knowledge, not just tutorials.

Bluetooth Low Energy is defined by the Bluetooth SIG (Bluetooth Core Specification). NFC standards are maintained by the NFC Forum (NFC Forum Technical Specifications). Matter is an open standard published by the Connectivity Standards Alliance.

Why Is BLE Integration the Most Common Failure Point?

Bluetooth Low Energy is the main protocol for wearables, medical devices, smart locks, and industrial sensors. Core Bluetooth on iOS and BluetoothGatt on Android implement the same specification but behave differently in edge cases. Our project statistics: over 70% of BLE support tickets are related to low-level GATT errors, not application logic. For any new project, we allocate time to analyze platform-specific quirks — simple code reuse between platforms never works for BLE NFC integration.

What to Do with Error 133 on Android?

Error 133 is the most common in Android BLE development. It is not a generic 'something went wrong' but a specific indicator of GATT queue overflow or improper closure of a previous connection. We fix it with two approaches. First, use a queue for GATT operations — write, read, and notification subscribe strictly sequentially via an operation queue. Second, always call disconnect() before close(). Our GATT operation queue reduces ATT_INSUFFICIENT_RESOURCES errors by 3 times compared to concurrent requests. Default MTU is 23 bytes. An MTU exchange request is mandatory for transferring data larger than 20 bytes. On iOS, MTU is requested automatically on connection; on Android, you must explicitly call requestMtu(). Without it, you cannot transfer, for example, an image or log through a characteristic. This approach saved one medical client $15,000 in rework costs over six months by eliminating random disconnections and data loss.

What Are the Key Differences Between HomeKit and Matter?

HomeKit is Apple's smart home ecosystem. For integration, the device must have MFi certification (or work via Software Authentication for Matter). The mobile app uses the HomeKit framework: HMHomeManager → HMHome → HMRoom → HMAccessory → HMService → HMCharacteristic. Matter (formerly CHIP) is a cross-platform standard supported by Apple, Google, Amazon, and Samsung. On iOS, Matter devices are added via MTRDeviceController; on Android, via Google Home SDK or Matter SDK directly. Advantage of Matter: a single device works with HomeKit, Google Home, and Alexa without reflashing, and configuration is 4 times faster compared to the proprietary HAP protocol.

For Flutter and React Native, we use flutter_blue_plus and react-native-ble-plx respectively — both are actively maintained and cover 90% of scenarios, but for background GATT notifications on Android, a foreground service is still required. Ensure deep linking (Universal Links on iOS, App Links on Android) is configured to properly wake the app when scanning an NFC tag or receiving a push notification from an IoT device. ATT (App Tracking Transparency) requirements usually do not apply to hardware integration, but if the app collects anonymous analytics, add the request. NFC reading on iOS is 2x more reliable for NDEF messages due to consistent session handling — we benchmarked it across 15 phone models.

NFC: Core NFC and Android NFC API

iOS supports NFC reading via CoreNFC since iOS 11, writing since iOS 13. Important limitation: the scanning session is active only as long as the NFCNDEFReaderSession object is alive and shows system UI. Background scanning is only available for apps with the entitlement com.apple.developer.nfc.readersession.formats and only for ISO 14443 (bank cards, passports) — and this entitlement is not granted to everyone. On Android, it is simpler: NfcAdapter.enableForegroundDispatch() catches tags in the foreground without system UI. Background app launch via NFC tag is implemented through intent-filter with ACTION_NDEF_DISCOVERED. Platform comparison for NFC:

How We Integrate BLE and NFC: Step-by-Step Process

1. Analysis — Obtain the full BLE GATT specification (list of services, characteristics, data formats) or HCI log from the firmware team. Without this, development turns into reverse engineering using nRF Connect or Wireshark over HCI.
2. Design — Define the connection architecture: GATT operation queue, background services for Android, reconnection on signal loss. Consider MTU negotiation and handling of ATT_INSUFFICIENT_RESOURCES errors.
3. Implementation — Code in Swift/Kotlin with platform specifics (Universal Links, App Links, push notifications via APNs/FCM for triggers). Use ProGuard/R8 (shrink) for Android code protection.
4. Testing — On real devices from day one. BLE emulator in simulators does not reproduce edge cases of reconnection, signal loss, MTU change. Use automation based on XCTest and Espresso.
5. Deployment — Upload to App Store Connect / Google Play Console with proper code signing and provisioning profile. For iOS — TestFlight, for Android — Firebase App Distribution.

For a tailored architecture design, contact our engineering team. We provide a free specification review within 2 business days.

What's Included (Deliverables)

• Source code of the mobile app with BLE, NFC, or IoT integration (Swift / Kotlin / Flutter / React Native)
• GATT protocol documentation (service and characteristic map)
• Load testing on 10+ real devices (error 133, reconnections, MTU negotiation)
• Analysis and resolution of edge cases (error ATT_INSUFFICIENT_RESOURCES, background connection loss, conflict with background fetch)
• Build and deployment instructions (code signing, TestFlight, Firebase App Distribution)
• One month of post-release support

We have completed 45+ projects with BLE/NFC/HomeKit. Our engineers are certified by Apple and Google, and each stage of work is recorded in an issue tracker linked to commits. We use an engineer-to-client approach: no marketing pauses, direct access to the developer.

Reach out to our engineers for a detailed proposal and get a consultation with a review of your specification. Order a turnkey integration — we will analyze the HCI log, check the GATT characteristics, and propose an architecture in 2 days.