Mobile UI for desktop

desktop

#21

Polite reminder, that there is a ready-to-use and working out-of-the box Desktop support for Flutter and if the company priority shifted at least a little bit from “promoting React-Native and FP” to delivering awesome app and user experience, you should have switched to Flutter yesterday:


#22

Interesting, where I can see the source code for this fork? Is this based on what?
Something funny is that you created a new account and it came preloaded with 625 SNT and some dust ETH. How is this possible? Also it forgot to ask confirmation of password?


#23

check the original post on this React-Native vs native mobile app - it’s just initial basic UI part, implemented in 5 hours with Flutter. I wrote 3 more mobile apps since then, and it’s just another league of mobile development compared to RN.


#24

Progress update:

Mobile UI:
Mobile UI for desktop was merged into master but it is not default UI for now. To take a look at it you can set flag MOBILE_UI_FOR_DESKTOP=1in .env file and run the app.

FlatList performance:
I made a few tweaks of performance and created a PR - https://github.com/status-im/react-native-desktop/pull/473.
Unfortunately I wasn’t able to add the most important tweak - asynchronous loading of qml components. When I tested it with internal js engine it worked well, but it crashes when I use node js engine. More work needed to manage work of different threads.

So for now FlatList is still unusable and I’m going to put it aside for a while and follow @andrey’s advice and reuse the same list as we use in current desktop UI (it is optimized on Qt side, not on js side as FlatList).


#25

meanwhile, Flutter team released Flutter for web developers preview, and here is how it looks like out of the box (with zero changes of the code):


#26

What would it take to hook mobile ui for desktop into an OS level interface so the wallet can be used for smart contract interactions? See https://frame.sh/ for an example.


#27

I’ve added MOBILE_UI_FOR_DESKTOP as an argument in the manual build:
https://ci.status.im/job/status-react/job/manual/build
If anyone wants to try that.


#28

Shouldn’t be too difficult, as far as I can see Frame is exposing a web3 provider on multiple endpoints ws, http, ipc and has extensions for browsers to inject and proxy to it. Doesn’t seem to do any magic beyond that.


#29

Thanks @jakubgs

status-desktop

and WOW @volodymyr.kozieiev this is incredible! the UI is way faster now (or maybe Its because I don’t have many chats :P) and looks so much better than before! Amazing stuff!