wire-ios VS GraphQLite

A better alternative to Signal is Wire https://wire.com/download

The Client is GPL-3.0 Licensed. (WebApp,Desktop,iOS,Android) The Server is AGPL-3.0 Licensed. Both Client and Server are Open-Source.

Wire iOS - 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.

Wire is also an open source encrypted messenger. They use the proteus protocol (an early branch of the Signal protocol), the implementation is called Cryptobox and is written in Rust, here is a Swift wrapper which their iOS app uses.

Single backend server (using GraphQLite)

For more details, please check the GraphQLite.com site.

There are probably million other ways to demonstrate how a SWAPI GraphQL endpoint can be accessed from an iOS app, but this is our version. You can check the full source code here.

If you prefer to make changes in the local database while the device is offline, and would like these changes to be synced automatically to the server (once the network connection is back live), then we need to set up Sync Engine.

With these code extensions, the device's local database (and the user interface) will be updated automatically by the server-side changes. You can check the full source code here.

Let's save the necessary Mutations and Queries into an appsync.graphql file, so we can simply use them in the codebase just referring to their names.

And pretty much that's all we need for the first working demo app. You can check the full source code here.

To solve all these issues, we have implemented GraphQLite. We believe this could be a solution for most of the database (local and remote) related challenges we are facing with. It might be the first step towards our goals being achieved.