2 ms·
What does the receiving user see? Do they know it was scheduled? If not they may expect me to start responding when I may be unavailable. What happens to read
by MBCook 4y ago
What does the receiving user see? Do they know it was scheduled?
If not they may expect me to start responding when I may be unavailable.
What happens to read status (when on)? I haven’t read your last X messages but I did send one to you? That’s off.
Can it be canceled?
How does this interact with the new function in iOS 16 letting you edit and delete after send?
Can I schedule send on my iPhone but edit before send on my iPad?
What if I schedule send and lose network. Then I edit on both my iPhone and iPad to show different things but they’re both off network. Not they both come back. What gets sent?
What if the ‘wrong one’ comes back first?
Does it work with SMS?
Lots of weird complications to think about.
- samatman 4y agoPersonally, I would solve all of these by pushing the message up, like sending it, but with colors that make it clear that it's suspended, and a clock icon, which shows when it will send. Long press the message to get a context menu: edit, delete, reschedule, send now. As for sync and all that, whatever algorithm they use for Notes is fine with me. I would expect the message itself to be living in iCloud until it's sent, so most of the questions about losing network connectivity or not having battery life wouldn't apply. So no, no SMS: support for SMS in Messages is an afterthought and I would in fact prefer two different apps, although I might be the only one who feels that way.
- jeroenhd 4y agoTelegram's implementation shows a little calendar icon next to the text input when you've planned a message, which takes you to a list of planned messages you can interact with like any other message. This solves the problem of your message appearing right in the middle of already sent messages or your message constantly bubbling down as a real-time conversation takes place. I think it works quite well.
- jeroenhd 4y agoUsing Telegram as a reference: - In the notification: yes. In the chat view: no. I don't know why it matters, though. If you expect an immediate response, you should probably use a more asynchronous communication method (many email platforms can hold messages for you). That doesn't seem like a reason to not make the feature available, though. - That's a possible state regardless, unless the client must always have a full database of all received messages before new messages come in; most messaging apps seem to support a "fragmented" read state and I doubt iOS's messenger doesn't. - Yes - I don't see the problem here. Replace the message in the queue using an account+message identifier/cryptographic signature/magical pixie dust. - Yes - If the message is sent by the server at the scheduled time, this isn't a problem. If you rely on individual devices (Google's implementation), you may end up sending a duplicate. I doubt this'll happen that often in practice. - Depends on the implementation; the server will probably keep the "correct" version to send. - Probably not? There are tons of features that don't work with SMS though. I haven't used SMS for years, but Google's Messages app has delayed messages and a web client, so this seems like a solved enough problem for those still using SMS. Several chat apps, including SMS apps, have this feature already. E2EE adds a layer of complexity but even that can be fixed with existing technology.