Jump to content
We apologize for the inconvenience, but chat support is currently unavailable. Please feel free to submit an email ticket or reach out at discussion.evernote.com. Thank you for understanding. ×

Ian Small

Evernote Staff*
  • Content Count

    30
  • Joined

  • Last visited

  • Days Won

    10

Ian Small last won the day on February 12

Ian Small had the most liked content!

Community Reputation

159 Seriously Awesome

About Ian Small

Profile Information

  • Subscription
    BUSINESS

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 1) I would be legitimately interested in understanding what others think the difference between these two things are. To me (admittedly, not having read the entirety of this 11-year-long forum discussion because I think the general drift is right there in the discussion thread title), they seem at first blush to be the same. Note: I think this is a question solely about notebooks, not about tags. 2) When we get on the other side of this huge lift we are in the middle of, I look forward to moving on to dealing with issues like putting this 11-year-long forum discussion to bed. Not next
  2. Quickie clarifications for those following along... Yes, per @jefito, Conduit is common *plumbing* on the client-side. Conduit has no relation to the UX. Every Evernote client built on Conduit could have a different UX and Conduit wouldn't mind. Users might mind, and we would definitely mind, but Conduit wouldn't. That's basically the whole point. Where Conduit figures in is anywhere that information flows between client and cloud - whether that information is content moving back and forth or a service call of some kind. We expect all of that information to flow through Cond
  3. Hello everyone... Just popping in on this discussion, if only because I don't really want @VisionCasting to carry out his friendly "threat". First of all, I'm sorry that this issue has been outstanding for so long. Second, I want to assure you that many things that may seem on the surface to be easy fixes can in fact be far from it. Sometimes, when we're not very responsive, it's simply because we have no good way to actually accomplish the fix, not because we think it's a bad idea. This is one such area. The way in which Evernote implemented sharing notes some years back was not
  4. Thanks for your request @s2sailor. Reminders are a hot topic across a number of different forum threads and social media conversations related to our efforts to converge the UX. Thread tone ranges from the productive ("what are you going to do with reminders?") to the understandably impatient ("why haven't you implemented reminders yet?") all the way to imminent doom ("oh no! they're going to take reminders away!"). In response to your constructive question - thank you! - let me provide the following update: 1. Reminders are used by a relatively small cross-section of our user populati
  5. Just to follow up on this, when Shane refers to "rules for contests", he's referring to laws. For all sorts of reasons, most of which are due to people or companies using some form of "pretend" contest to take advantage of consumers in the past, most countries have developed a fairly detailed set of laws and regulations that apply to any entity trying to run a "contest" open to their residents. If you are a company like Evernote that does business globally, you have to pay attention to each country's laws if you are going to run a contest open to residents of that country. As you can pr
  6. Hi all - I just realized we did not follow up in this channel as I had committed earlier about the most recent Safari Web Clipper release, although it's probably hard to miss with the big banner at the top of the screen. Nonetheless, here is the relevant announcement: A continuing thank you for your patience ian
  7. @hksmith I think it's safe to say we'd neither want you dead, nor in the water, nor any combination of both. As @DTLow pointed out above, we are expressly acknowledging that our modern web experience does not yet have all the functionality we'd like it to have, and all the functionality it needs in order for it to meet a reasonable bar for all of you. Things like reminders are an excellent example of the gap. Lack of support for nested tags is another. Missing features like this that are key to some folks' workflows are one of the reasons - but not the only one, I should caveat - that
  8. Experts say: Yes, the refinement suggestions supplied in the menu are based on the current search scope. At the beginning, the scope is "All Notes". From that point forward, as you build a search iteratively, the search won't (at least, should not! 🙂 official allowance for product-feature-not-in-GA-yet) suggest something that isn't contained in the current scope. To @Jason Goldsmith's question, if you used the tag portland as your first scope refinement (however you enter it, by pulling it off the search menu or typing tag:portland), the suggestions provided should only be those that ma
  9. Stacey - If I understand your question correctly, I think the answer is "yes". If you look carefully at this part of the video: https://youtu.be/_ZJqSR_MWmw?t=218 you can see the option to save as a shortcut as well in the dialog box allowing us to save the search. If that's not what you mean, please ask again! Back to lurking... ian
  10. Hi Everyone - Following up on on my post from Thursday night... We snuck in another build/review cycle over the weekend when our QA team, who have been continuing to validate our candidate releases over the past days, found a bug that merited our holding the release. As of this moment, Apple has approved that most recent build and we have released it to the App Store. As you may know, it takes a while for builds released to the App Store to propagate through to global availability, so we anticipate that it will be visible to all of you by Tuesday morning, likely at this URL: https
  11. Hi Everyone - Following up on on my post from Tuesday... As you may have guessed by now, our first submission to the App Store was bounced back to us by Apple, as they identified a number of (non-bug) issues they wanted us to fix before they would approve it. We have fixed those issues, and have submitted an updated build for their review as of a few hours ago. This set of posts from me has been pretty extreme in terms of transparency with where we are in the process, but I think in the circumstances this is the right way for us to communicate with you. As before, I have to point
  12. Hi Everyone - I’m following up on my post from Friday. A few hours ago, we submitted an initial, reduced-functionality release of our Safari 13-compatible Web Clipper into Apple’s review process. As some of you may know, the review process for App Store submissions can be a bit of a black box, both in terms of how long it takes and whether a submission will get through successfully. However, given how long it’s taken to get to this point, I thought it was appropriate to let you know that we are making concrete progress towards having an initial Safari 13-compatible release of our W
  13. Hi Everyone - I’m following up on my post from ten days ago. In that post, I had indicated that we were trying to get an initial, reduced-functionality release of a Safari 13-compatible Web Clipper into your hands this week, but that there was still significant work remaining. Today is Friday of that week, and clearly we have not met our goal. We have a working build, but it is not yet release-quality. We are continuing to work on bugs, on stability and on CPU utilization issues in order to converge on something releasable. We will be working through the weekend. I’m sorry th
  14. I'm sorry that we were not able to get a fixed/compatible version of Penultimate fixed prior to the GM release of iPadOS. The process for us to fix the iPadOS incompatibilities proved trickier than it should have been. A new release of Penultimate that is compatible with iPadOS was submitted into the App Store review process a few hours ago. As some of you may know, the review process for App Store submissions can be a bit of a black box, both in terms of how long it takes and whether a submission will get through successfully. But I thought it was appropriate to let you know that (fin
  15. Hi Everyone - First, I want to apologize that we're all here. Because you’re rightfully complaining about something that should never have happened. I take ownership of it. This year for us has been all about making very hard decisions around competing priorities, and on this one, we erred. We had expected that Apple would release Safari along with macOS Catalina later in October. When Apple released Safari on Sept 20th, we were surprised, we weren’t ready, and we ended up leaving you out in the cold. Even with the release date being pulled in, that shouldn't have happened. Ap
×
×
  • Create New...