Qortal Project

The future of blockchain platforms

User Tools

Site Tools


qnect_app

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
qnect_app [10/17/2022 06:10] gfactorqnect_app [11/17/2022 18:49] (current) – [Phase 1 Notes] gfactor
Line 2: Line 2:
 {{:qortal_official_logo_transparent_.png?400|}} {{:qortal_official_logo_transparent_.png?400|}}
  
-Qnect is our upcoming cross platform chat app! For Android, Linux and Windows this app will be available as a native build, which means the packages are built specifically for each of those platforms and will not be dependent on or require any additional software to run. It has not yet been decided if the Android version will be available through the Play store or as an unofficial apk.+**Current Phase:** Phase 1 (0.1.2 - Beta) 
 + 
 +Qnect is our cross platform chat app! For Android, Linux and Windows this app is available as a native build, which means the packages are built specifically for each of those platforms and will not be dependent on or require any additional software to run. It has not yet been decided if the Android version will be available through the Play store or as an unofficial apk.
  
 Qnect will also be made available as a web app that can run on all devices (including iPhone and Mac). The web app can be opened in a web browser by going to the Qnect website and in most cases can be installed to your home screen or desktop as a progressive web app. It will probably also be possible to run your own local HTTP server and install the app on that server. This still needs to be tested and all scenarios need to be considered before deciding whether this is a viable option but it is within the realm of possibilities. Qnect will also be made available as a web app that can run on all devices (including iPhone and Mac). The web app can be opened in a web browser by going to the Qnect website and in most cases can be installed to your home screen or desktop as a progressive web app. It will probably also be possible to run your own local HTTP server and install the app on that server. This still needs to be tested and all scenarios need to be considered before deciding whether this is a viable option but it is within the realm of possibilities.
Line 42: Line 44:
  
 So yes, compared to the UI, Qnect is more centralized, but it's as decentralized as we can expect it to be for a mobile app that is meant to be used outside of our home network. So yes, compared to the UI, Qnect is more centralized, but it's as decentralized as we can expect it to be for a mobile app that is meant to be used outside of our home network.
 +
 +===== Phase 1 Notes =====
 +
 +Hello all.
 +
 +The Qnect PWA is live!
 +
 +Now that the progressive web app is deployed everyone should be able to use the app, regardless of which device or operating system you are using. As long as you have a modern web browser you'll be able to load the web app in your browser and install it to your device as a 'pseudo-native app'. This means that Qnect will run as a stand-alone application but within the framework of the browser from which you've installed it. 
 +
 +If you choose to install Qnect as a PWA it will in principle only be dependent on the Qnect website for the initial installation and to update the app when a new version is released. In theory, the Qnect website could be taken offline and everyone who has installed the PWA will still have a functioning application. I'm considering taking down the site for a while after enough people have installed the app in order to test/prove this premise.
 +
 +Using the PWA version of Qnect as opposed to the native builds has some advantages and some disadvantages:
 +
 +Advantages:
 +
 +- Very easy to install.
 +- The app will automatically update when a new version is found on the website.
 +- Available for all devices and operating systems.
 +- Circumvents big tech gate-keeping infrastructure such as the App Store or the Google Play Store.
 +- Significant increase in potential user-base due to the much lower barrier for getting started.
 +- Experience is similar to a native app while allowing for cross platform deployment.
 +- Offline availability, can still function if the Qnect website goes down.
 +- Can access additional services and hardware on your device if granted those permissions.
 +
 +Disadvantages:
 +
 +- Not all browsers support installing a web app as a PWA (Firefox comes to mind).
 +- Deployment aimed at non tech users requires a (centralized) web server, technically inclined users could install the PWA over their own their own server and domain name using SSL or TLS.
 +- Features such as link/image preview and push notifications which are available for native builds will not be available for the PWA or require external solutions.
 +- Native builds will most likely perform better than the PWA, though the difference will likely be negligible on modern devices.
 +
 +
 +Check it out at https://www.qnect.org
qnect_app.1666001415.txt.gz · Last modified: 10/17/2022 06:10 by gfactor