# Discourse forum owners: Are you interested in native mobile apps?

**URL:** <https://meta.discourse.org/t/discourse-forum-owners-are-you-interested-in-native-mobile-apps/127456>\
**Category:** Marketplace\
**Created:** [3 september 2019 om 05:23 UTC](https://meta.discourse.org/t/discourse-forum-owners-are-you-interested-in-native-mobile-apps/127456 "2019-09-03T05:23:04Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![Aa7](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/aa7/32/199103_2.png) [@Aa7](https://meta.discourse.org/u/Aa7)\
**Post date:** [7 september 2019 om 03:11 UTC](https://meta.discourse.org/t/discourse-forum-owners-are-you-interested-in-native-mobile-apps/127456/18 "2019-09-07T03:11:46Z")

</div>

> [@bartv](#):
>
> How would you keep up with changes? Would it support plugins?

This is great question. I’d hope that the API versioning in Discourse follows the [semantic versioning](https://semver.org/) approach (it’s one of the things I’ll have to verify). That way, when there’s an incompatible Discourse update, an app update will have to follow.

The less critical thing would be keeping up with incremental feature updates that don’t make breaking changes to the API. I’ll obviously need to keep a regular schedule of updates to keep up with something like this.

I think supporting the most popular plugins (for example, ones offering by Discourse’s own hosting) would be a start (and a given).

In the case of plugins not on that list, I think we can keep adding support as the number of people needing it goes up. I guess there is a threshold for when supporting a plugin becomes a must have. I don’t know yet what that threshold is. Maybe I’ll be able to prioritize development for an obscure plugin if someone has a strong reason to have it on the app.

---

_[View the full topic](https://meta.discourse.org/t/discourse-forum-owners-are-you-interested-in-native-mobile-apps/127456)._
