有效处理推送通知
我对推送通知有疑问。
每当推送到来并且用户正在某个 XYZ 控制器上工作时，推送需要初始化并显示另一个控制器。现在，我应该在当前活动控制器之上显示推送控制器，并在完成后将用户带回到当前工作的控制器吗？
如果推送控制器涉及一些操作并且是与其关联的完整功能集，该怎么办？当压力来临时我们是否应该限制行动？
什么是最好的交易？
I have a query regarding push notification.
Whenever a push comes and user is working on some XYZ controller and push requires another controller to be initialized and shown. Now should I show the push controller on top of the current active controller and take the user back to the currently working controller, once done?
What if the push controller has some actions involved and is a complete set of functionality associated with it. Should we restrict actions when a push comes.
What is the best deal?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这在很大程度上取决于应用程序的流程和组织。在基于选项卡栏的应用程序中，您应该有一个用于处理通知活动的选项卡，并为相应的 UITabBarItem 放置一个 badderValue。您还可以显示一个警报，提供切换到另一个选项卡上的“处理通知”区域的可能性。选项卡栏是“同时”访问不同流并在它们之间来回切换的好方法，而无需自己管理保存和恢复 VC 流。
It depends heavily on the flow and organization of your application. In a tab bar based application, you should have a tab for handling the notification activity, and place a badgeValue for the corresponding UITabBarItem. You could also show an alert offering the possibility of switching to the "handle notification" area on the other tab. Tab Bars are a good way of having "simultaneous" access to differing flows and switching back and forth between them without having to manage saving and restoring the VC flow yourself.