You can find the published source code at github.com/wireapp/wir….
For licensing information, see the attached LICENSE file and the list of third-party licenses at wire.com/legal/licen….
a. You agree not to change the way the Open Source App connects and interacts with our servers; b. You agree not to weaken any of the security features of the Open Source App; c. You agree not to use our servers to store data for purposes other than the intended and original functionality of the Open Source App; d. You acknowledge that you are solely responsible for any and all updates to your Open Source App.
For clarity, if you compile the open source software that we make available from time to time to develop your own mobile, desktop or web application, and do not cause that application to connect to our servers for any purposes, then that application will not be deemed an Open Source App and the foregoing will not apply to that application.
No license is granted to the Wire trademark and its associated logos, all of which will continue to be owned exclusively by Wire Swiss GmbH. Any use of the Wire trademark and/or its associated logos is expressly prohibited without the express prior written consent of Wire Swiss GmbH.
The Wire mobile app has an architectural layer that we call sync engine . It is the client-side layer that processes all the data that is displayed in the mobile app. It handles network communication and authentication with the backend, push notifications, local caching of data, client-side business logic, signaling with the audio-video libraries, encryption and decryption (using encryption libraries from a lower level) and other bits and pieces.
The user interface layer of the mobile app is built on top of the sync engine, which provides the data to display to the UI. The sync engine itself is built on top of a few third-party frameworks, and uses Wire components that are shared between platforms for cryptography (Proteus/Cryptobox) and audio-video signaling (AVS).
The iOS application follows closely the overall mobile architecture, adding its layers of iOS and UI helpers.
ZMessaging-cocoa is the top-most layer of the iOS sync engine, and it is using on a number of lower-level frameworks.
- zmessaging-cocoa: topmost layer that implements client-side business logic, caching, encryption and client-side backend communication protocol
The project in this repository contains the Wire iOS client project. You can build the project yourself. However, there are some differences with the binary Wire iOS client available on the App Store. These differences are:
- the open source project does not include the API keys of Vimeo, Localytics, HockeyApp and other 3rd party services.
- the open source project links agains the open source Wire audio-video-signaling (AVS) library. The binary App Store client links against an AVS version that contains proprietary improvements for the call quality.
In order to build Wire for iOS locally, it is necessary to install the following tools on the local machine:
The setup script will automatically check for you that you satisfy these requirements
- Check out the wire-ios repository.
- From the checkout folder, run
./setup.sh. This will pull in all the necessary dependencies with Carthage and CocoaPods and verify that you have the right version of the tools installed.
- Open the workspace
- Click the "Run" button in Xcode
These steps allow you to build only the Wire umbrella project, pulling in all other Wire frameworks with Carthage. If you want to modify the source/debug other Wire frameworks, you can open the
Carthage/Checkouts subfolder and open the individual projects for each dependency there.
You can then use
carthage build --platform ios to rebuild the dependency and use it in the umbrella project.