Single unified UI for OrganicMaps #9407

New issue

Open

opened 2024-09-30 15:15:15 +00:00 by pktiuk · 0 comments

pktiuk commented

2024-09-30 15:15:15 +00:00

(Migrated from github.com)

Is your feature request related to a problem? Please describe.

With this raw idea I want to tackle several issues:

Linux desktop interface seems to be lagging behind (does not look very well, is not convergent, does not work well with touch and in general is not very familiar for people using it on mobile devices).
There is no online/web version of organic maps and creating it would require also creating new UI again
Developing several UIs in parallel seems to generate a lot of overhead for developers
Developer willing to add some UI features (for example like adding new button for changing building color) to this app needs to setup several development environments and needs to test it several times (setup env on linux, later install, android studio, and later buy a mac and setup environment for iOS)
This repository uses multiple languages for different modules: Python, C++, Java, Swift, which makes reviewing and development difficult.

Describe the ideal solution

There is a single convergent and universal frontend for this entire app working with all (or at least most) of target platforms.
Currently, there are a lot of technologies and libraries which could be used for this purpose. Some example technologies:

QML - part of QT library, which can target many types of targets
Flutter or flutter-based bindings like flet (linked issue: organicmaps/organicmaps#9292 )
Kivy
Compose Multiplatform - framework developed by JetBrains
Xamarin
Dioxus

Selecting one of them is a big decission, which should be taken by Organic Maps dev team

Describe alternatives you have considered

Use web technologies and create simple Electron based app
Create a regular desktop app which could be compiled into WebAssembly and somehow package it for multiple platforms
Changing just a framework for desktop UI for something mode cross-platorm (but without mobile support) like iced

Additional context

I just wanted to contribute something to the place editor UI and I saw, that it would require a lot of changes in multiple clients. So I gave up.

This issue could result in implementing another, more universal frontend which could be developed concurrently until it would be mature and could replace other frontends one by one.

Labels for this issue I find relevant: Desktop, Android, iOS, DevEx, Raw Idea, UI, UX

**Is your feature request related to a problem? Please describe.** With this raw idea I want to tackle several issues: - Linux desktop interface seems to be lagging behind (does not look very well, is not convergent, does not work well with touch and in general is not very familiar for people using it on mobile devices). - There is no online/web version of organic maps and creating it would require also creating new UI again - Developing several UIs in parallel seems to generate a lot of overhead for developers - Developer willing to add some UI features (for example like adding new button for changing building color) to this app needs to setup several development environments and needs to test it several times (setup env on linux, later install, android studio, and later buy a mac and setup environment for iOS) - This repository uses multiple languages for different modules: Python, C++, Java, Swift, which makes reviewing and development difficult. **Describe the ideal solution** There is a single convergent and universal frontend for this entire app working with all (or at least most) of target platforms. Currently, there are a lot of technologies and libraries which could be used for this purpose. Some example technologies: - QML - part of QT library, which can target many types of targets - Flutter or flutter-based bindings like [flet](https://flet.dev/) (linked issue: https://git.omaps.dev/organicmaps/organicmaps/issues/9292 ) - [Kivy](https://kivy.org/) - [Compose Multiplatform](https://github.com/JetBrains/compose-multiplatform) - framework developed by JetBrains - Xamarin - [Dioxus](https://github.com/DioxusLabs/dioxus) Selecting one of them is a big decission, which should be taken by Organic Maps dev team **Describe alternatives you have considered** - Use web technologies and create simple Electron based app - Create a regular desktop app which could be compiled into WebAssembly and somehow package it for multiple platforms - Changing just a framework for desktop UI for something mode cross-platorm (but without mobile support) like [iced](https://github.com/iced-rs/iced) **Additional context** I just wanted to contribute something to the place editor UI and I saw, that it would require a lot of changes in multiple clients. So I gave up. This issue could result in implementing another, more universal frontend which could be developed concurrently until it would be mature and could replace other frontends one by one. Labels for this issue I find relevant: Desktop, Android, iOS, DevEx, Raw Idea, UI, UX

👍 3 👎 2

This repo is archived. You cannot comment on issues.