Project

General

Profile

Feature #11354

implement native mobile client

Added by Greg Shah 4 months ago. Updated 4 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

Related issues

Related to User Interface - Feature #11353: implement support for deployment of the web client as a mobile application using capacitor and/or apache cordova New

History

#1 Updated by Greg Shah 4 months ago

  • Related to Feature #11353: implement support for deployment of the web client as a mobile application using capacitor and/or apache cordova added

#2 Updated by Greg Shah 4 months ago

The idea is to implement a true mobile client for FWD.

On Android, it has support for Java so we could potentially port our existing Java client implementation (or most of it depending on the features) to the mobile platform. The primary issues here would be how well some of the features port and how heavyweight the client would be (may not be reasonable for mobile). The big advantage would be not having to spawn a JVM for each client.

For iOS and even for Android (if the above idea is not suitable) we could implement the mobile equivalent of the web client. A split-design plugin that has part running in a spawned JVM and the other part running natively as a mobile application. As with #11353, we would have to support the packaging/inclusion of enough configuration and settings UI capability to connect the web client to the customer's FWD server.

Also available in: Atom PDF