AppCenter Submission: App Not Accepted

[cassidyjames]

Hey @meisenzahl, thank you for another app submission to AppCenter! After a review of your app, we have determined that it is considered a web app. As listed in the Publishing Requirements:

Your app may be written in any language, but the front-end must be a native GTK3 app. Web, Electron, Qt, Java, and other non-native app front-ends will be rejected during the review process.

We have since amended the requirements to clarify cases like this:

While apps can have web components using a native WebView, such apps must add substantial functionality to the web content, or the majority of the interface that a user interacts with must be native GTK3. Apps that primarily wrap an existing website or websites will likely be rejected.

We hope this does not deter you from submitting future apps that are supported! Let me know if you have any questions and I would be happy to answer them.

[meisenzahl]

Thanks for your feedback!

So far I have used apps like Franz or Rambox as multi messaging app. I use different messengers like Telegram, Slack, WhatsApp, ... Being able to use them all in one app is an advantage for me.

When using the above mentioned apps, I was always bothered by little things. Therefore I started the development of this app and I already use it as a daily driver. If I need a feature, I build it into the app.

I have already noticed that Messages is much more resource efficient than the above mentioned apps, which both use Electron.

Planned features

Attention mockups ahead ;)

Adding more messaging platforms

I would like to support more messaging platforms.

At the first start of the app and in a settings menu you should be able to select the required messaging platforms.

Native notifications support

The messengers notifications are already displayed as native notifications.

Messages should count the notifications and display the number in the GUI. In addition, the number of unread notifications should be displayed as a badge icon on the app icon.

If possible, Messages should be opened and the corresponding messenger displayed when you click a native notification.

The feature was already merged with #4

@cassidyjames it would be nice if you could estimate if Messages could meet the AppCenter requirements in the future.

[cassidyjames]

@meisenzahl those sound like handy additions, but I think the problem comes down to the majority of the UI the user cares about and will be using day-to-day is actually a third-party web app—while I understand the want for an alternative to heavier Electron apps, I don't think the addition of those features would put this into native app territory.

A route you might pursue would be publishing your app as a Flatpak on Flathub, where there are not as strict requirements around apps as with AppCenter. Users of elementary OS will still be able to easily install your app with the “Install” button on the Flathub website, and will get updates via AppCenter. Of course if the app substantially changes in the future, you would be welcome to submit a new release for further review and potential inclusion in AppCenter.

[checor]

Hello @meisenzahl, I'm using your app and I like it! It's easier to manage messages in a single app, rather than juggling between web tabs or electron apps.

I'm seeing that the issue is that AppCenter requires the app to be more native, and not rely that much on a webview. Do you think is a laudable task to begin a transition to a native app? I know Whatsapp doesn't offer a API that you can use for messaging, but maybe Telegram can achieve that.

Great work!