A fast file transfer app that doesn’t use data
Zapya is an Android app that lets you transfer files to others without an Internet connection, a Wi-Fi network or a USB cable.
If you frequently send files to family, friends and coworkers and want an easier way to do that, then Zapya may be just what you’re looking for. Zapya is simple to use and has a clever user interface that will have you up and transferring files in no time. File transfers are fast whether you’re transferring to a friend, transferring to an entire group, sharing via a folder or backing up your device data. The app even makes it simple to replicate your phone so that you can restore it later on.
The app uses Wi-Fi direct for near sharing. This doesn’t require Internet, a Wi-Fi network connection or any cables. Two or more devices simply connect to each other via Wi-Fi and communicate. Transfers are fast and, in fact, 100 times faster than Bluetooth. You can also transfer to those who aren’t in close proximity by using the Internet or uploading to a cloud folder that they can access whenever.
You can transfer to one other user at a time, but you can also establish groups. Create a group of friends or family members, for instance, and they’ll automatically get the photos and other items you send. Zapya also isn’t limited to just Android. It also supports Apple and Windows computers and devices, and while this app is at its most convenient when all users have Zapya installed, that isn’t a requirement either. There are several different ways to transfer from an Android device to an Apple or Windows computer or device and vice versa.
- Send files to friends and groups with ease
- File transfers are 100 times faster than Bluetooth
New Zapya 4.6
1. Enhance user interface;
2. Enhance recommending experience in personal profile.
3. Redesign of Transfer History screen.
4. Fix bugs
Potentially dangerous permissions
- CAMERA: Required to be able to access the camera device.
- GET_ACCOUNTS: Allows access to the list of accounts in the Accounts Service.
- READ_CALL_LOG: Allows an application to read the user's call log.
- READ_CONTACTS: Allows an application to read the user's contacts data.
- READ_EXTERNAL_STORAGE: Allows an application to read from external storage.
- READ_PHONE_STATE: Allows read only access to phone state, including the phone number of the device, current cellular network information, the status of any ongoing calls, and a list of any PhoneAccounts registered on the device.
- READ_SMS: Allows an application to read SMS messages.
- WRITE_CALL_LOG: Allows an application to write (but not read) the user's call log data.
- WRITE_CONTACTS: Allows an application to write the user's contacts data.
- WRITE_EXTERNAL_STORAGE: Allows an application to write to external storage.
- ACCESS_NETWORK_STATE: Allows applications to access information about networks.
- ACCESS_WIFI_STATE: Allows applications to access information about Wi-Fi networks.
- BIND_ACCESSIBILITY_SERVICE: Must be required by an AccessibilityService, to ensure that only the system can bind to it.
- BROADCAST_STICKY: Allows an application to broadcast sticky intents. These are broadcasts whose data is held by the system after being finished, so that clients can quickly retrieve that data without having to wait for the next broadcast.
- CHANGE_NETWORK_STATE: Allows applications to change network connectivity state.
- CHANGE_WIFI_MULTICAST_STATE: Allows applications to enter Wi-Fi Multicast mode.
- CHANGE_WIFI_STATE: Allows applications to change Wi-Fi connectivity state.
- GET_TASKS: This constant was deprecated in API level 21. No longer enforced.
- INTERNET: Allows applications to open network sockets.
- MOUNT_UNMOUNT_FILESYSTEMS: Allows mounting and unmounting file systems for removable storage.
- RECEIVE_BOOT_COMPLETED: Allows an application to receive the ACTION_BOOT_COMPLETED that is broadcast after the system finishes booting. If you don't request this permission, you will not receive the broadcast at that time. Though holding this permission does not have any security implications, it can have a negative impact on the user experience by increasing the amount of time it takes the system to start and allowing applications to have themselves running without the user being aware of them. As such, you must explicitly declare your use of this facility to make that visible to the user.
- SYSTEM_ALERT_WINDOW: Allows an app to create windows using the type TYPE_SYSTEM_ALERT, shown on top of all other apps. Very few apps should use this permission; these windows are intended for system-level interaction with the user.
- VIBRATE: Allows access to the vibrator.
- WAKE_LOCK: Allows using PowerManager WakeLocks to keep processor from sleeping or screen from dimming.
- WRITE_SETTINGS: Allows an application to read or write the system settings.