from a calendar entry, from a contact entry, from a note or an action, etc.).Īpplying a reasonably limited interface strategy for mobile messengers could bring significant better user experience, while not compromising EPIM for Desktop functionalities.Į.g. The limited mobile messenger interface strategy does only allow to trigger activities in EPIM modules (contact creation, action creation, notes creation, calendar entry creation) or trigger sending of messages out of EPIM modules (e.g. Not supported could be category management, EPIM attachments, etc. Only EPIM functionality which is compatible with open mobile OS interface technology is supported. the omitted use of category management for messages, etc.Īpplying the interface strategy could allowĬ1/ to trigger message sending from EPIM for Android or EPIM for iOS from contacts, notes, actions, calendar through a messenger services which is reachable via the mobile OS interface, andĬ2/ to transfer messages from a messenger service to EPIM for Android or EPIM for iOS via the OS interface into the modules notes (create a note), calendar (create a calendar entry), actions (create an action), contacts (create a contact). eMail, SMS, WA, FB, Threema, Line, Viper, Telegram, Signal).ī/Open mobile OS technology (rather than proprietary solutions):Īs there are many messenger services, it could make sense to only use open (rather than proprietary) interface technologies of the Operating Systems (Windows, Android, iOS) accepting limitations in EPIM functionality on mobile OS (compared to already provided functionality of the EPIM desktop version). It would be good if EPIM would apply a reasonable interface strategy with the various messenger services (e.g. eMail) integration with EPIM for Android or EPIM for iOS, but a limited approach: I would not recommend to implement a full blown messenger services (e.g.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |