humanengr

I pm’d everybody above a couple of weeks ago and 1 added a vote (after some difficulty). Ever since that voting mechanism was instituted, I’ve written in repeatedly about its invisibility, awkwardness, general poor implementation, etc., etc., and the fact that people aren’t using it because they don’t notice it, but the damn thing hasn’t changed. Maybe if you create a ticket on your own for that??

To promote this suggestion, tap the up arrow at the top to the left of “Annotation Summary …”.

To anyone who likes this suggestion (to show all annotations for a pdf), pls tap the ‘up arrow’ at the top left of this page by my OP. Evernote implemented a non-obvious voting mechanism that generally goes unnoticed. (And it’s not that the votes mean much, but it does show support.) thx

Also, removal of this feature was -not- announced in the release, so waiting for 8.1 was not an adequate strategy. In good news, Support filed a 'formal' request with Dev; some changes are in process there, one consequence of which might be more thorough release notes.

Agree. As a matter of general principle, feature loss for whatever reason is not a plan -- particularly for a tool that is a core element of user workflow. Features should not be removed but rather added at least as (and preferentially as user-configurable) options on all platforms. In a broader sense, is a feature reduction as it makes the app substantially less usable. I raised the issue for user-configurability of the formatting bar with Support and that was passed to the Dev team. Perhaps the same could be done for other contexts, e.g., the home page as well.

I’ll say this: It’s not available on MacOS. Apparently to cohere the platforms, they removed the feature on iOS rather than make it available on all platforms. I relied on it and can't wait for restoration. Beyond that the particulars don’t matter here.

Agree. Further re missing features: the Dev Team continues to remove more features in 8.1. I have communicated with Support re the particulars, am waiting to see how quickly this is rectified, and won't get into a conversation about it here except to say this is enough to have broken my trust in EN, am exploring alternatives, and will move on if this is not quickly fixed.

Aah … I see that after our PM conversation you edited your note: from 'your' to 'my' in the first part and added the second part. As I said earlier: But the effect of telling others, e.g.: is contra the interests of community of users when considered as a whole, and EN (and Apple) in the long run. [I've edited the above in consideration of the PM conversation you initiated. Perhaps we can make further progress there and more completely resolve the issues.]

As I said, you can't: This responds to one requirement -- not the requirements as a set (much less the broader context previously stated).

@DTLow, you didn't respond to because you can't.

Did you read the post linked below?

Note the lack of 1) apology for past behavior and 2) commitment to refrain from doing same for future releases.

Exactly. No other iOS app gets such a pass. Such encouragement requires users to expend more effort because of an app's poor quality assurance (updating apps individually, monitoring forums, …); fosters habits at EN that further this trend; drives customers to other products; and degrades the whole platform. Naive and harmful, @DTLow

Apparently not in reading or writing. That is in no way shape or form what I said. Again, shifting responsibility.

By your own statement, the testing process was not complete before 8.0 was released. You are, by placing quality assurance responsibility on users rather than EN and beta testers.