Extend react-native-desktop to support status-react Desktop functionality about swarms HOT 10 CLOSED

@vkjr @narek-h
To start discussion of Goals and Implementation plan, we might set following as first goals:

• Enhance development cycle to get acceptable performance (adopt figwheel + live-reload, find the way to compile ClojureScript to JS without code optimization (lein has known issues with that), build in parallel for mobile to be sure in compatibility ( ? but it seems we need this only if we can't have 100% code compatibility with available status-im code for mobile ))
• Make few ClojureScript code screens fully supported by Qt based port ( UI code + 3rd party plugins code ). Separate list of issues and not yet supported things by priority should be created.

from swarms.

@vkjr @flexsurfer Idea is updated according to the latest discussions, please, feel free to contribute if something missed, etc, thanks!

from swarms.

@MaxRis. thanks! I also updated "Title" in Preamble section to match the name of idea and added one more exit criteria - "Existing UI for status-react desktop runs smoothly with react-native-desktop
"

from swarms.

@vkjr Goals and title are updated, could you please verify if it's fine, thank you!

from swarms.

Once we will have at least few screens of status-im fully supported by react-native-desktop, it might be good sign that react-native-desktop is ready for Desktop specific implementation with ClojureScript and status-im core team can try to start with Desktop version based on react-native-desktop.

from swarms.

@MaxRis, agree with proposed steps

from swarms.

@MaxRis, @narek-h, if we look at the code of different screens, we can find that every screen uses quite a lot of 3rd party libraries and react native components.
For example chat screen (which would be nice to have early due to importance) depends on:
3rd party libraries: svg, i18n, invertible-scroll-view, config, emojis, orientation, drawer, realm
react-native components/APIs: Alert, Animated view, dimensions
So, it can take time until we see full chat screen. And if we measure progress in screens, we are going to be demoralised :)

Most of the 3rd-party libraries and react native components used by code in components and utils folders in status-react. chat screen depends on components: vector-icons, status-bar, chat-icon, listview, toolbar-content, animation, list-selection

So I would suggest to start supporting separate components and utils and track them as progress steps. They are more predictable. To support vector-icon component we need to implement raeact-native-svg library. To support config util we need to implement react-native-config library. And so on.

from swarms.

Probably first components I would start with are: vector-icons, i18n, chat-icon, action-button

from swarms.

hey @vkjr , what is chat-icon? and we don't need action-button for desktop

from swarms.

Replaced by https://github.com/status-im/ideas/blob/master/ideas/34-react-native-qt.md

from swarms.