That apps published there can't be wrappers around a web application.
Good rule, those should be web addresses, not apps. Or even better, native applications rather than web apps, but it does depend on the context.
Eh... why? More to the point, it's not mentioned anywhere in their guidelines, it was made up on the spot by the fella doing the code review.
They are inefficient and bloated.
And personally, I prefer good reasoning over good rules. If something comes up that is a bad idea but there's no existing rule against it, the rules should be changed to address it. As long as the reasoning is sound, I think it's a good thing, especially when we're talking about something like a software distribution platform as opposed to say laws that determine freedom or imprisonment.
Also if you've made a web app, let it be installed as a web app. Both FF and Chrome let you install web apps in one click.
Inefficient and bloated describes 90% of all apps I've ever seen, regardless of technology used, so I fail to see your point.
If you really want to have it available on F-Droid, you can always put it in a separate repository. So I can see it being annoying that they reject it from their repo, but there's still a reasonable path forward.
Well, I have the app on Google Play store, which was originally meant to be the alternative, now it's the main store.
What's a wrapper in this context?
An app that's just WebView?
Not WebView, but a so-called TWA, aka Trusted Web Activity, a features specifically designed to wrap PWAs and give them full-blown app capabilities.
What additional capabilities does that give the app beyond using Firefox or Chrome to install it as a PWA?
That apps published there can't be wrappers around a web application.
Good rule, those should be web addresses, not apps. Or even better, native applications rather than web apps, but it does depend on the context.
Eh... why? More to the point, it's not mentioned anywhere in their guidelines, it was made up on the spot by the fella doing the code review.
They are inefficient and bloated.
And personally, I prefer good reasoning over good rules. If something comes up that is a bad idea but there's no existing rule against it, the rules should be changed to address it. As long as the reasoning is sound, I think it's a good thing, especially when we're talking about something like a software distribution platform as opposed to say laws that determine freedom or imprisonment.
Also if you've made a web app, let it be installed as a web app. Both FF and Chrome let you install web apps in one click.
Inefficient and bloated describes 90% of all apps I've ever seen, regardless of technology used, so I fail to see your point.
If you really want to have it available on F-Droid, you can always put it in a separate repository. So I can see it being annoying that they reject it from their repo, but there's still a reasonable path forward.
Well, I have the app on Google Play store, which was originally meant to be the alternative, now it's the main store.
What's a wrapper in this context?
An app that's just WebView?
Not WebView, but a so-called TWA, aka Trusted Web Activity, a features specifically designed to wrap PWAs and give them full-blown app capabilities.
What additional capabilities does that give the app beyond using Firefox or Chrome to install it as a PWA?