You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UI of the public QFieldCloud at https://app.qfield.cloud is totally different from the UI you get when self-hosting the application. This also includes the URL scheme which affects functionality like the 'edit on QField cloud' button in QFieldSync that will try to open https://{HOST}/a/{USER}/{PROJECT}.
Are there plans to align both solutions. If so, will the self-hosted solution look more like the public site or the other way around? Is there a reason why both are so different?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The UI of the public QFieldCloud at https://app.qfield.cloud is totally different from the UI you get when self-hosting the application. This also includes the URL scheme which affects functionality like the 'edit on QField cloud' button in QFieldSync that will try to open https://{HOST}/a/{USER}/{PROJECT}.
Are there plans to align both solutions. If so, will the self-hosted solution look more like the public site or the other way around? Is there a reason why both are so different?
Best regards.
Beta Was this translation helpful? Give feedback.
All reactions