# \[DONE\] Mobile Apps (Apple, Android)

**URL:** <https://community.fibery.io/t/done-mobile-apps-apple-android/985>\
**Category:** Mobile\
**Tags:** mobile\
**Created:** [September 16, 2020, 9:25pm UTC](https://community.fibery.io/t/done-mobile-apps-apple-android/985 "2020-09-16T21:25:12Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [September 22, 2020, 3:34am UTC](https://community.fibery.io/t/done-mobile-apps-apple-android/985/6 "2020-09-22T03:34:02Z")

</div>

> [@B\_Sp](#):
>
> Yes, for all intents and purposes a “responsive” type approach, for example, to the web interface that would scale on tablet and mobile would be useful for sure. I want to stress though that in my case, the. notifications element is something my team really falls back on. We are trying to find a solution that lets us use our main “goto” Work Mgmt solution for as much communication as possible. Using two solutions simply leads to too much good info, content, ideas, etc. getting lost in the other tool.

Good to hear. Regarding notifications, of course the regular web version is also not yet adequate in this way, in my opinion at least. So it’s a problem to solve overall. My understanding though is that there are ways that a mobile-oriented website can generate notifications for mobile OSs. So that could be solved without an app as well: [Notifications &nbsp;|&nbsp; web.dev](https://developers.google.com/web/fundamentals/push-notifications)

---

_[View the full topic](https://community.fibery.io/t/done-mobile-apps-apple-android/985)._
