# iOS App It's time to talk about it **URL:** \ **Category:** Mobile Apps\ **Created:** [October 31, 2018, 9:38pm UTC](https://forum.mattermost.com/t/ios-app-its-time-to-talk-about-it/6064 "2018-10-31T21:38:53Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![RbDev](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/rbdev/32/1827_2.png) [@RbDev](https://forum.mattermost.com/u/RbDev)\ **Post date:** [October 31, 2018, 9:38pm UTC](https://forum.mattermost.com/t/ios-app-its-time-to-talk-about-it/6064/1 "2018-10-31T21:38:53Z")
Hi all, It is very sad to see an app like that performing so pourly. Using it feels like using a limited browser and it should be far from that since it’s a native app. - The app struggles to handle wireless connections issues. “connecting” “connected” “pull to update”. - It takes time to display messages. - It is always “loading”. - The updates are not fluid. The screen is always blinking. - Lack many features available in the browser. - Asking for user intervention whenever there is an issue. “please push to reload”, “click to try again”. Why doesn’t it behave like any other native app such as imessages or skype or whatapp or hipchat or slack? The app doesn’t feel solid. MM iOS native app is crude and it’s been many months without any major improvement. I think its time for you guys to seat down and rethink the hole thing. Look into your competition and compare with your current app. Plan what needs to be achieved and design a solid app’s core to be able to handle it. Let the app get the message data, save it locally and handle them as required. Layout and other features. Develop a smart app. If disconnects display a notification but as soon as it reconnects, resume activities on its own. Queue users commands in the app like sending or modifying messages and execute them when possible. I’m here if you need input/feedback. Cheers ---
**Author:** ![amy.blais](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/amy.blais/32/7481_2.png) [@amy.blais](https://forum.mattermost.com/u/amy.blais)\ **Post date:** [November 1, 2018, 2:54pm UTC](https://forum.mattermost.com/t/ios-app-its-time-to-talk-about-it/6064/2 "2018-11-01T14:54:10Z")
Hi @RbDev, Feedback is much appreciated! I have forwarded it to our mobile app team and I’ll let you know their thoughts. ---
**Author:** ![mattermut](https://avatars.discourse-cdn.com/v4/letter/m/779978/32.png) [@mattermut](https://forum.mattermost.com/u/mattermut)\ **Post date:** [January 22, 2019, 7:40am UTC](https://forum.mattermost.com/t/ios-app-its-time-to-talk-about-it/6064/3 "2019-01-22T07:40:54Z")
Do you got any thoughts from your mobile app team since Nov '18? Please share it with other readers too. Thank you! ---
**Author:** ![amy.blais](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/amy.blais/32/7481_2.png) [@amy.blais](https://forum.mattermost.com/u/amy.blais)\ **Post date:** [January 22, 2019, 7:12pm UTC](https://forum.mattermost.com/t/ios-app-its-time-to-talk-about-it/6064/4 "2019-01-22T19:12:40Z")
Hi @mattermut, A summary of our discussion with `RbDev` can be found here on our community instance: [https://community.mattermost.com/core/pl/u1n5yit3xjg6pmgbgbftmur9ha](https://community.mattermost.com/core/pl/u1n5yit3xjg6pmgbgbftmur9ha). Also, a list of Jira tickets were opened for improving app behaviour during poor network: [https://mattermost.atlassian.net/browse/MM-13065](https://mattermost.atlassian.net/browse/MM-13065) ---
**Author:** ![dannymohammad](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/dannymohammad/32/2489_2.png) [@dannymohammad](https://forum.mattermost.com/u/dannymohammad)\ **Post date:** [January 23, 2019, 2:14am UTC](https://forum.mattermost.com/t/ios-app-its-time-to-talk-about-it/6064/5 "2019-01-23T02:14:24Z")
Hi, everyone. In case you would like the visibility of the discussion performed without going to the Community instance: **_Missing messages_** : [Missing Messages on iOS App](https://forum.mattermost.com/t/missing-messages-on-ios-app/6046) Repro (not consistent): User gets a notification, opens from tapping on notification or just opening the app, new messages coming in, but the message from the push notification is missing in the post list. Without intervention, missing messages don’t appear ever. Force refresh (pull up) then the messages appear, or if cache is reset Suggestion 1: When app gets focus, send a ping to server to check the latest message in the channel and compare it to the latest message on the server. If client is behind, pull the messages in order Suggestion 2: Easy fix: force to refresh when app is focused **_Duplicate messages being sent_** Repro (not consistent): Send a message in a bad network (ie metro), observe occasionally the message is posted twice (duplicate messages are visible on webapp and in database as well) Suggestion: Messages should each have unique ID and the server checks the ID to make sure it shouldn’t post it again. **_Android Server URL issues_** Repro: Logging out and trying to switch servers, enter in a new server, but it cannot connect and doesn’t let the user past the server URL screen Work around: Force restart the app (only works once) **_Session expiry not sending push notifications_** Feedback that the session expiry time should be longer or removed by default. Hope that helps. The mobile team hears you, so stay tuned as they address each issue one by one.