rts

When I first investigated sideloading I learned that it was possible to download Android APK files directly from the Google Play Store's website. Given that the Play Store will still install v8.13.3 for versions of Android earlier than 10 it should be possible to grab an officially blessed APK file that way. As to third-party sites, APKPure.com has an entire archive of Evernote versions up to 8.13.3. I've never seen evidence that APKPure's files contained malware or viruses, despite the question coming up frequently (viz Quora last month). Indeed, once you've installed v 8.13.3 ( after you've disabled automatic updates!) I would expect Google's Play Protect function to complain if it found something amiss.

My reference to a roll out schedule was tongue-in-cheek. It's pretty clear at this point that forecasting is not the company's strength. My point was that by six months after a product's release it's silly to excuse limitations and persistent problems as mere rollout issues. A 10k note limit in v10 when the Legacy apps and "Classic" web UI have no such limit begs the question: why was this limit added to v10? Why exclude some Premium customers from using a different web UI? A vaguely plausible explanation would be their "always online" design for v10 clients has an intractable limit that slows sync requests on large note collections to a glacial pace. Not really a response you can hand to the customer support team. Especially when you'd previously told them their all purpose response should be 'you need to upgrade to the latest version of v10'. Using extreme programming or agile development as a description however is a bit of a red herring given that v10 was introduced as a replacement, not a technology preview. (I have no problem with a rolling release schedule BTW; Arch is my favorite Linux distribution.) If a product is still in beta yet management declares it gold and releases it to customers, it's hardly the fault of the development team. Oh, PinkElephant, you dare to dream big. I salute you!

I'm in almost the same boat as you. I don't have any Apple devices however and my most recent Android devices are only up to Pie (9). My options for satisfying any v10 curiosity were the PC desktop (never again) and the web. In the past I'd used the web interface on the rare occasion I was restricted to a Linux box. Nowadays Android tablets, VNC, and SSH have removed even that use case. So it appears I'll be sticking to Legacy versions for the remaining months of my Premium subscription. There are worse fates.

I have no doubt, er, little doubt you are correct. This begs the question of how many months of v10's deployment can be honestly be described as a roll out. In a little over a week it will be six months since that accursed Evernote email notice arrived to tell me "The new Evernote is here." Certainly customers should be advised of a roll out schedule, no? I've received no such notice from the company. Without your help I wouldn't have realized I was a second class Evernote Web citizen. This morning I tried web access again and was rewarded with a large popup notice asking if I wouldn't like to try the new Evernote Web. Remembering I'd been there before I closed my eyes, took a deep breath, and briefly recited the new Evernote Serenity Prayer, "Fine. Whatever." Although clicking on the notification did make it disappear I didn't see any other activity. I switched to another desktop for a while but when I returned there still didn't seem to be a difference. I thought perhaps I needed to log out for the change to take effect, but after logging out and a few hours later back in, no dice. The company still only deems me worthy of v5.33.0, an abandoned project. And so it goes.

My only choices were those indicated in the image: that version or the previous version. Frankly, it never occurred to me that my choices for a web interface would somehow be dictated by the number of notes in my database. What possible difference could it make for an interface design? But at 11k notes I would probably be over the threshold you mention. The software design decisions of this company continue to amaze.

At a glance I appear to be using Evernote Web v5.33.0 from Firefox on a Windows 10 PC. I'm guessing you were using something else.

Hmm, ehrt74's response doesn't seem particular detailed. I wonder why. Out of curiosity I just checked a tablet equipped with Android Evernote V8.13.3 (June '20 release) and the sidebar, for example, seems indistinguishable from the new, improved web version. That said, I must recant a previous criticism of Evernote when comparing it to Joplin. A check today showed both apps returning proper results for Japanese, Russian, German, et al. The lack of search results I previously noted had only been observed using the New! Improved! web interface. That would be same interface that flashed the New! Improved! red alert box announcing a sync error had occurred. Repeatedly. Over an ethernet connection. Perhaps ehrt74 meant to write "FIRST DECENT SYNC ERROR MESSAGES" earlier? Or perhaps the vague arm-waving response was simply an homage to the level of detail in Evernote's feature roadmap for v10. Just kidding, ehrt74. The v10 web interface does feature a new "View options" button. Unlike last year's Android release, however, clicking the button doesn't reveal any options. Just a text box announcing: Well, perhaps my memory is playing tricks on me with the last two sentences.

This would be a more relevant argument if people in this thread were complaining about XML or the API. But they aren't, are they? They're complaining about the client software and (especially) the poor decisions being made by Evernote the company. Your TLAs aren't magic shields that can protect you from Ian Small. Your Joplin comment manages to be both ignorant and specious. The GitHub version of Markdown is widely used but even if Joplin used a lesser known version of Markdown I wouldn't care. Joplin's export options include HTML and PDF -- both of which I think you'll grant are reasonably standardized. I suspect you also don't realize the advantages that the simple text format at the heart of Joplin provide: faster and more versatile searches than Evernote provides. If I want to drop a dubious equation into a note I can either take advantage of the included KaTeX feature and jot down "$$ \pi=22/7 $$" for a centered equation as found in books or simply "π=22/7" for inline text. Similarly, if I were to make notes on this thread I'd probably be using "バカ!" a lot. While both Evernote and Joplin allow the use of katakana in a note only Joplin will return search results. Unless you count Evernote's "No notes found" as a search result.

Wow, that seems unduly harsh. DTLow has merely adopted the iffin'-it-ain't-broke-don't-fix-it approach to an established workflow using the Legacy version. That's a perfectly reasonable approach for some people. Others of us have found it time to move on and started exploring or actually migrating to other software. A mild sense of panic or being peeved can be useful if used to spur one to action. In any event, Ian Small's never seeing another dime of my money. Not addressed to me, but for what it's worth here are a few thoughts from someone who's shifted to using Joplin unless a feature of Evernote is absolutely needed. I mostly used Evernote to write notes, import PDF documents, and search through that information. On the writing notes part Joplin is perfectly usable and the search aspect is much faster than Evernote. When it comes to OCR, however, Joplin is not (so far) a viable option. It's one thing to be able to insert a screenshot or attach a PDF to a note as a record for research, taxes, expense reports, etc. Creating a note that supports searching the text of a PDF or an image is a different matter entirely. Can you get around that limitation through external programs or the creative use of tags, sub-notebooks, etc.? Absolutely. Will that workflow be as easy as it used to be in Evernote? Probably not. On the first few pages of this thread you can read people's woes because their fonts and carefully tweaked note formats were altered by v10. I'd be surprised and happy to discover they've found alternatives that didn't muck with their carefully crafted note designs. I'm not optimistic about their options. Certainly Joplin is not that alternative.

We are in violent agreement on almost all points. The difference seems to be you define "support" along the lines of "it was working the last time I checked" and I define it along the lines of a product warranty. Your Windows XP computer in the attic might still "work" but that doesn't mean you should expect support from Microsoft. The API being rock solid doesn't mean jack if you rely on access to servers you don't control. Evernote has shown they can add and kill program features and subscription terms whenever they wish. Hell, Ian Small's opinion of tags seems to have changed in the short time since the initial v10 release. A stable API is no guarantee of future support for application features or existing workflows. Or Legacy client access for that matter. Of course there's always a chance that the trust you, PinkElephant, and other loyalists demonstrate is justified. I might be unduly skeptical of the customer support to be expected of an erstwhile sock company. Time will tell.

Oh, there's no question that Legacy works. For now. It could continue to work fine for another decade or HQ could hit a kill switch tomorrow. But if you started having syncing problems tomorrow is there any doubt in your mind that making a support request would result in anything other than "You need to upgrade"? In addition to Legacy for Macs and PCs the company has also (inadvertently) introduced Android users to the joys of sideloading as their route to a Legacy equivalent. I'm not sure if that qualifies as a public service or not.

Officially v10 is the only "supported" version. So I guess it has that going for it. The company has it own sound reasons for the shift to v10 but customer satisfaction doesn't seem high on their list. Releasing v10 in such an unfinished state has been pretty much a disaster. You should bear in mind the company has clearly stated that they are making the Legacy version available for download but it is no longer a supported product and will only be available until v10 had reached some unspecified feature set. So your ability to download Legacy could end at any time. Are they specific on how long Legacy will be allowed to work or which Legacy features v10 will eventually support? No. Indeed, we've already seen some features are trimmed back substantially. So now some people who depend on particular Evernote features are using Legacy but also tracking v10 in hopes the beta period will end with it having the features they want/need.

I have stopped tracking v10 iterations because I find other hobbies more rewarding. And it would be a hobby at this point. (I use PC and Android devices, so PinkElephant's cheerful Mac/iOS reports are irrelevant to my situation.) I check this forum from time to time to learn from other people's workflow and alternative product reports. As a Premium account holder I'm using the Legacy grace period to verify Joplin meets my needs. EN as a company has simply lost my trust.

Since you're a big fan of information perhaps you'd like to share with the rest of the class your evidence that EN is indeed "clawing back to offer working v10 clients." Because a lot of people keep using words like "slow", "buggy", and the like. When someone complains they find 10.6.9 unusable on a Mac that is in fact useful information. It might not be at the level of detail to help developers fix problems or to warn users which particular features to avoid, but it's not the ****ing job of paying customers to help a company debug software that should never have been released in such a state.

As Grand Moff Tarkin once put it, you're far too trusting. Once you've concluded that v10 should have been presented as a preview/beta/work-in-progress instead of as "the new Evernote" you have to ask yourself, why was it released in that shape? The missing features people have complained about aren't bugs, they're design decisions. Ditto for the font choice limitations, etc. So why should we believe that the company will "fix things" when management has already given the green light to reduced functionality? It seems to me there are three explanations for the premature v10 release: 1) management thought the product was "close enough" for most users (viz Small's statements on tags), 2) some idiot(s) thought adding features to a released product would be easy, or 3) v10 was pushed out for reasons unrelated to customer acceptance, such as being evidence the company was meeting milestones. I'm inclined to think it's a mix of all three, but none suggest that customers using the Legacy apps will see all the features they rely on appear in v10. On the contrary the company has declined to make explicit promises on how long the (already unsupported) Legacy version will be available or what specific features v10 will have when it's "finished". I think the customer venting, er, feedback is useful should someone at the company actually pay attention to the posts. Given Small's shifting assessments of v10's meeting people's needs I suspect the feedback is being mostly ignored at some point in the chain of command, but one can hope. As to this particular forum discussion, I've learned a lot from the posts detailing how people are using Evernote and the experiences of people migrating to other software.