I’m guessing there are good reasons for this or you would have already implemented, but it seems strange that when I invoke link mode, the parentheses appear to the left of cursor, rather than surround the cursor position so I can simply type the URL. I have to move the cursor, an unnecessary step.
Also, it seems un-sleek that I need to type “http://” and “.com”. Drafts is normally much more helpful than that, so I’m disappointed that no context-sensitive prompts appear around my keyboard.
See what happens when you spoil your users? We get lazy and demanding!
Sorry, I’m at the stage where I can use the app, mostly, but am not always sure what things are called.
If I’m typing a draft and want to live-link some text, I select the text and hit the link icon just above keyboard. In this before/after screenshot, my cursor position (which you can’t see in screenshot) is to right of parenthesis, so I need to back it up one position to type URL.
Also I’d like help typing out “http://”.
It dawns on me that this is oriented to pasting in links from clipboard rather than typing them out. So my use case might be minority, hence the issues (like I said, I figured there were good reasons for it being this way).
Iit is worse than you might imagine. There are currently over 1.5K TLD and while http is a common web protocol I think https is more common these days, and there are other protocols and registered schema.
The efficiency is always going to depend on the set of sites a user wants to reference in real life. This approach wouldn’t work for me but if the OP mainly references sites that match the described constraints, then it would save time.
I can’t see it being particularly useful to most people, as most I would expect would encounter different URLs regularly and more often than not I suspect would have them on their clipboard.
I think TextExpander for a TLD would not save much time if any. For a URL, absolutely.
A prompt could help but if in the existing flow might slow it down overall. As an additional action it might be just as fast to manually edit.
My point is simply that this approach http /.com approach is probably only really a practical solution for a very small subset of users. I don’t think there’s anything much to be gained on building out the above. I’d suggest it would be better to apply options on top of other more mainstream link actions.
Er, I’m figuring we needn’t offer every top-level domain to provide some broad convenience to a broad swathe of users in a broad swathe of cases. It’s non-agony to type a suffix; this is just a small boost for most-frequent case.
I totally agree.
I love the workflow of the original action.
My links enter drafts mostly via the share sheet template anyway. And we have some quite nice examples in the forum to fetch the title of the http-url in a draft.
Writing urls does seem to much effort to me. (manly working on iOS)