Built on our patented FASP transfer technology, Aspera Mobile Apps for iOS and Android transfer large files over Wi-Fi and cellular networks at speeds that are up to 100X faster than traditional mobile transfer technologies.

NEW: Aspera Files Mobile for iOS and Android 1.0

A new Files Mobile app 1.0 for iOS and Android, is available on the iOS App Store and Google Play Store. This new app works in conjunction with the Aspera Files SaaS supporting mobile uses cases. Based on Aspera's high-speed FASP transport core, Aspera Files Mobile lets you contribute content from mobile devices to Files instances via anonymous personal or dropbox invites including the ability to enter custom metadata.

To send a package from within the app itself, users first select a saved invitation, enter the subject and any notes, select the files they wish to send, fill in any required metadata, then send the package. To send a package from another app, select assets from within the app, share those with the Files app, select a saved invite to send the package to, then follow the same steps as if you were in the app. It's that easy.


  • Supports mobile content contribution to Aspera Files public / anonymous invites by sending packages.
  • Supports phone and tablet form factors.
  • iOS: Supports Slide-Over and Split-View modes on iPad.
  • iOS: Integrates into iOS Preferences to expose basic preferences in the standard preferences app.

Public invites

  • Supports "me" (submit to person) or dropbox (submit to dropbox) invitation types from the Files web app.
  • Invites can be automatically added from the email where they are received (or any other app opening links)
    • iOS: The Files web app itself supports deep linking to the iOS app.
    • Android: The Files app is automatically launched
  • Invites can be cut-and-pasted into the app.
  • The user can share an invite added to the app.
  • The user can delete an invite added to the app.
  • iOS: 3D touch support (on 6s and 6s+ and up phones -- 3D (deep) touch on app icon in home view gives menu of defined submission destinations, for rapid access to initiate a package submission.

Package composition / submission

  • All forms of metadata (text, textarea, single list, multiple list) are supported for dropbox submissions.
  • Packages can be constructed with assets from:
    • iOS: camera, gallery, or other apps that support document sharing
    • Android: camera, or other apps supporting sharing files
  • App displays assets with thumbnails or icons which resemble the type of assets
  • User can delete selected asset before sending the package
  • App shows information about required metadata not filled-out yet
  • App can be accessed via Share button from any app supporting that to allow users to compose a package
    • iOS: The user does not leave the app, a popup to compose a package appears
    • Android: The user is redirected to a new activity to compose a package
  • After completing the packages details / metadata, and the user sending the package
    • IOS: The transfer happens in the foreground and awaits completion to navigate the app
    • Android: The transfer happens in the background and a notification is displayed in the notification center
  • Android: Notifications are displayed for transfers in the notification area. A failed transfer can be retried from the notification

Package transfer history

  • The app includes a screen to show the history of package sending.
    The user can retry a failed transfer

Aspera Mobile Uploader for Android 1.0

Based on Aspera's high-speed fasp transport core, Aspera Mobile Uploader lets you upload files to mobile-enabled Aspera transfer servers.

To use, select one or more images, videos, files, etc. from any app that supports sharing, share with the Uploader, then upload to defined accounts. You can monitor your upload via the Android notification center. It's as simple as that...

Highlights of the Aspera Uploader:

  • Upload from photo/video collections, or files created by other apps on your device.
  • Upload single or multiple items from any app that supports Android's native sharing functionality, including typical photo and video apps.
  • Items being uploaded will use Android file names but can be easily renamed before uploading.
  • Prefixes and suffixes may be specified for file names, and will apply to each uploaded asset in a set of multiple assets.
  • View the transfer status and final results in the standard Android notification area, where the notification can be deleted when no longer needed.
  • Define and use multiple Aspera transfer server accounts.
  • New accounts are validated when defined so they can be counted on to work when actually used later for uploading.
  • One or more destination directories can be defined for any account, allowing uploads to be directed to specific locations on the specified Aspera server.

To use this app, at least one account on an Aspera transfer server is required, and your transfer server(s) used by the app must also be mobile-enabled. The minimum server level for Aspera transfer servers is 3.4.

Aspera Mobile SDK for iOS and Android

The Aspera Mobile SDK for iOS and Android 3.6 are new mobile SDKs for iOS and Android to simplify the use of the fasp protocol within mobile applications.

  • Simplified transfer-oriented model
  • APIs are lighter and slimmed-down to ease integration and comprehension
  • Similar API across both iOS and Android
  • Supports regular and persistent fasp sessions
  • iOS SDK supports Swift and Objective-C
  • Android SDK distribution support Android Studio and Eclipse ADT development environments
  • Improved documentation with more examples and code snippets
  • Each SDK ships with sample programs to demonstrate use of the SDK

These new SDKs are now the strategic SDKs being used by Aspera in our mobile apps. The Android SDK replaces the earlier Android SDK from the ADN. The iOS SDK is now the primary mobile SDK for iOS in the ADN, while the earlier queue-based iOS SDK will remain in the ADN for the foreseeable future.

Aspera faspex Mobile for iOS

Based on Aspera's high-speed FASP transport core, the Aspera faspex Mobile app allows you to receive and send packages between your mobile device and your faspex server.

The new Aspera faspex Mobile v3.0 for iOS is a major version, primarily focused on being used as a share extension to send content from other iOS apps, e.g. photo gallery, voice recorder, etc.

Features include:

  • As a share extension, the app now supports creation and sending of packages from within other apps that support the iOS native sharing paradigm, including the iOS Photos app for photos and videos
  • To use, select assets from your iOS app, share them with the Aspera faspex Mobile app, and select an account and a destination on that account. You are then shown the normal faspex package creation views to enter package details, including metadata if required.
  • Support for additional metadata and metadata attributes for faspex 4
    • Metadata field labels with long names are now presented in an improved fashion.
    • The app will now support maximum field lengths of metadata items if specified from the server
    • Support for the new Faspex 4 “date” metadata type
    • The app will now remove specified characters from metadata fields if so configured on the server
  • Support custom dropbox/workgroup inbox destinations
  • Multiple SAML providers in conjunction with Faspex 4 are now supported
  • mp4 and other related media types are now represented by a specific thumbnail
  • When iOS settings changes are required, the app now sends the user directly to the Settings app, to simplify changing those affected settings. If the user was in the middle of package composition, that fact is remembered for when the app is restarted after the setting change(s)
  • The app size has been reduced to enable faster downloading and upgrading
  • Compatibility with IPv6 DNS64/NAT64 networks


Using the new Faspex v4 API, faspex Mobile for Android 3.0 provides more complete support for dropboxes and metadata, with improved UI/UX to match Android Material Design guidelines. It requires Faspex 4 on the server side. The existing Faspex Mobile for Android app will continue to be supplied in the near-term for Faspex 3 customers. 

Improvements over current Android Faspex client include

  • Uses Faspex v4 API exclusively (requires Faspex 4) 
  • Updated UI/UX to match Material Design Multi-select when adding attachments 
  • Support for server default metadata profile for normal packages 
  • Support for archiving and permanently deleting packages and improved API for archive actions 
  • Leverages Android Account Manager for features such as periodic account configuration/package list sync, account management through Android Settings 
  • Support for date type metadata fields 
  • Pull-down-to-refresh in inbox view 
  • SAML support