Proposal: disable community projects tab in QField in certain cases

[woutergd]

Describe the issue

For certain projects we are working on, we want to use QField. However, the UI of QField provides for inexperienced users way too many buttons and options that can cause issues or wrong buttons to be pressed, so we want to have it as clean as possible.

One of these issues we encounter is during the initial sign in / loading of a project process. The community tab with public projects is always shown, while most of the times this is empty.

We would like to propose a change that this tab can be hidden, either automatically when no public projects are found, or based on a flag on the QFieldCloud server that can be linked to a user or subscription, or even server-wide.

If we implement this change, would this fit the design of QField and be accepted? Or are there already ways to implement / modify this behaviour?

[nirvn]

@woutergd , have thought about this a bit, we'd be perfectly fine having the community tab disabled if the endpoint URL (i.e. cloudConnection.url) isn't *.qfield.cloud. That'd be an acceptable change we'd merge right away :)

I think on the longer run, we'd want a QFieldCloud server capabilities listing or something (that's passed on by the server when logging in or validating the session token), but IMHO, it'd be an overkill at the moment.

[m-kuhn]

@woutergd , have thought about this a bit, we'd be perfectly fine having the community tab disabled if the endpoint URL (i.e. cloudConnection.url) isn't *.qfield.cloud. That'd be an acceptable change we'd merge right away :)

👍

I think on the longer run, we'd want a QFieldCloud server capabilities listing or something (that's passed on by the server when logging in or validating the session token), but IMHO, it'd be an overkill at the moment.

I think this would need a cross-check with the QFC team (CC @suricactus) for a proper architecture

[suricactus]

It is not clear to me if the community tab is empty when using the service at app.qfield.cloud or a on-premise installation @woutergd . I would assume the same as @nirvn that we talk about on-premise installation and I do agree with the proposal that the community tab makes sense only for the service provided under the *.qfield.cloud domain.

[woutergd]

@m-kuhn @nirvn thanks for the feedback, we will propose a PR within the upcoming weeks with a check in the way as you propose. It is indeed currently for a self-hosted / onprem Cloud-instance, but I can imagine that in the future some kind of configuration for this can be helpfull.