Jump to content

Ian Small

Evernote Staff*
  • Content Count

  • Joined

  • Last visited

  • Days Won


Ian Small last won the day on November 3

Ian Small had the most liked content!

Community Reputation

123 Awesome

About Ian Small

Profile Information

  • Subscription

Recent Profile Visitors

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

  1. 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
  2. @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 we've not yet formally made the modern web experience our GA release and become more enthusiastic about promoting people off older versions of our web client. That being said, the majority of our web users find the upsides of this newest version worth some of those compromises. It's our job over time to maximize the upside and minimize the compromises. To get there, we still have work to do at many levels in the code, including UX, functionality and plumbing. You've seen some of that in the investments we've been making in the new editor (which you can all experience now), in the new search implementation (watch here if you haven't encountered it yet), and in other areas as well. And with the new search implementation, you've seen us not just improve search, but also close the gap around creating and accessing saved searches - one of the gaps mentioned in the list that @DTLow highlighted in his post. As to your specific ask, we've already looked at various different ways to bring reminders into this experience. We're still discussing how and when to do so. But one way or another, we'll get there. Back to lurking ian
  3. 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 make sense in that context. To his point, he'd get food, tourism, accommodation, history, and transportation suggested as tag refinements. (He might not get all of them at the start because of space limitations, but as he started to type, they'd narrow in and get suggested.) . He wouldn't get sunshine as a suggested tag, on the assumption that it's unlikely that there would be a note tagged with portland *and* sunshine (herewith a formal apology to all insulted portlandians for that needless cheapshot; my excuse is that it's late on a Friday night). On the other hand, if he'd started his search scope with honolulu, sunshine might get suggested as a tag refinement. To a couple of @jefito's questions: First, at 4:54 (after the initial typo for tag:succlent is corrected to tag:succulent), you can see we provide the same filtering suggestions that we do if you'd typed "succulent" or "succ" and clicked on the tag in the drop down. Second, the focus for this design and implementation has been on providing a more powerful search capability and demystifying the search interface for the largest cross-section of users we can target. We wanted to avoid disempowering our super-pro users, so we made sure that the advanced search syntax still works. And where it made sense, we tied the advanced search syntax back into the interactive mode. What we haven't done (at least at this stage) is try to wire some of the suggestion and auto-completion capabilities into the middle of entering advanced search terms - so, as you pointed out, couldn't we have either offered to auto-complete tag:succ into tag:succulent or auto-correct tag:succlent into tag:succulent? Answer, yes, of course; but at this point that's not where we've invested the engineering effort. For better or worse, that's been a conscious decision and how we've tried to accommodate both worlds right now at this point in redesigning and improving search. We need to see how this design plays in the real world to figure out where we should next invest energy. We do have some further work already queued in the hopper to fully finish what we view as the first full phase of this work, but it requires more heavy lifting in the back-end before we can wire it all up, so it's waiting on a much longer pole. In the meantime, we want to make sure what we have is working well, make sure we continue to tune it, observe performance in the wild and tune/improve as needed, and learn at scale in the real world to determine the next most impactful place for us to focus our search-related energies. All in all, search occupies about 1/3 of May's time across her part of the product function portfolio. So it's a big, ongoing deal for us and for her. Back to lurking for real this time ian
  4. 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
  5. 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://apps.apple.com/us/app/evernote-web-clipper/id1481669779?ls=1&mt=12 If you are a Safari web clipper user, our marketing and customer support teams will attempt to reach you directly to inform you of the release. And there will be follow up communications tomorrow detailing the complete list of the features in (and not yet in) this first, reduced-functionality release of our Safari 13-compatible Web Clipper. I apologize again for our taking this long to get to this first release. We will be continuing to push on our end, working to fill in the remaining gaps and fix any bugs we discover until we once again have a full implementation of the Web Clipper in Safari. More info on those subsequent releases to follow in this channel when we have something useful to say. ian
  6. 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 out that the review process for App Store submissions is a bit of a black box, both in terms of how long it takes and whether a submission will get through successfully, but we are hopeful that this build will meet with Apple's approval. Finally, we will post again once this first version of the Safari 13-compatible Web Clipper is available in the App Store, including a complete list of the features in (and not yet in) this release. And we will follow up with additional posts as we proceed forward into the subsequent releases that fill in the gaps and fix any bugs we discover until we once again have a full implementation of the Web Clipper in Safari. ian
  7. 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 Web Clipper in your hands. As I have said previously, this first release will have reduced functionality. In particular, while most of the Clipper’s core functionality is included in this release (e.g. all clipping formats, screenshot and annotate capabilities, support for notebook selection, tagging and remarks, as well as PDF clipping), there are a number of features that have not made it into this build. Any one of these may be core to your particular workflow, and may result in this initial, reduced-functionality release not living up to your expectations. To that end, we have not stopped working. Our intent is to fast-follow this initial release with subsequent releases that fill in the gaps and fix any bugs we discover until we once again have a full implementation of the Web Clipper in Safari. We will, of course, post again once this first version of the Safari 13-compatible Web Clipper is available in the App Store, including a complete list of the features in (and not yet in) this release. And we will follow up with additional posts as we proceed forward into the subsequent releases. ian
  8. 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 that it is taking this long. As explained in my original post, it is not as simple as recompiling, and we are encountering more challenges than we expected. We will provide another update next week. ian
  9. 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 (fingers crossed) we are making progress towards rectifying the problem. We will, of course, post again once an updated version of Penultimate is in the store. ian
  10. 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. Apologies aren't worth much compared to actions, but know that you have my apology for this. Prior to the 20th, we had thought we were on track. Part of our engineering work was focussed on the changes Apple had made in their plugin architecture. But another part of the engineering work was focussed on re-plumbing a large chunk of the web clipper internals to match other work we are doing across all of the clients in support of improved reliability and sync. Because of the way the engineering work had been structured, when Safari 13 came out, we didn't have a releasable set of code that we could quickly bundle up and get into the catalog. Instead, we have had to re-order the work to get to something releasable, with the goal of getting you all back on a path to a fully-functional Web Clipper in Safari as soon as possible. So as has been suggested above, we will be first releasing a reduced version of the Web Clipper for Safari to deliver you core pieces of the functionality you are currently missing. That first release will not be a complete replacement of all the functionality that works in Safari 12 today. We will fast-follow that initial release with subsequent releases that fill in the gaps until we once again have a full implementation of the Web Clipper in Safari. Our goal is to have that initial release into your hands next week, but I should underscore that we still have real work to do to get to a sufficiently stable build that we are comfortable releasing. As you are all probably aware, there is an entire rollover of Apple’s software platforms taking place in a 45-day period at the moment. That's been challenging to manage. If I could go back to do it all over again, we would have been ready with the Safari Web Clipper. Which means there are lessons for us to learn in balancing priorities. I apologize again that we didn't get it right. We are taking all the actions at our disposal, including literally working around the clock to get the software you need back in front of you again. ian
  11. Shortest response to all speculation above: we have been investing for the last several months in replacing the plumbing in client apps, including in the modern web experience. When we are done (we aren't, yet) this will mean a common codebase shared across all the clients for cloud-client functionality such as sync, which should help us both isolate and stamp out bugs as well as driving more consistent behaviour across any user's Evernote experience that spans multiple devices. None of the previews put out to date incorporate any of this work, which is foundational to implementing the local data store for desktop and mobile clients that we all know and love. We plan to shoot a Behind the Scenes video that talks about the new plumbing, but the architect we need for that is ... ahem ... busy right now, or else you would have seen it before this one! Side by side installations on desktop machines of the beta and of a current production release will have distinct local data stores; you will be able to use both at the same time (I do that, right now). Back to lurking ian
  12. Thanks for the feedback. I suspect a part of the vertical spacing on mobile is driven by a desire for each item in the list to be easily selectable, and the reality that some people (like me) have relatively - um - broader fingers than others. (Otherwise known as the "fat finger problem".) . That being said, completely understand the underlying impact on information density and will make sure that the point gets raised and considered. Re the grey, I'm assuming you are reacting to what you saw in the video, not to an actual build or similar screen you saw somewhere. I say this because the relative contrast that gets picked up and displayed when we make printouts, stick them on a surface, and then shoot them again with an HD camera is not all that representative of what it actually looks like on a mobile screen. (Limitations of the quick-and-dirty production process for the Behind the Scenes videos.) . If you're reacting to a screen in your current mobile app that you think is representative of the contrast problem, please let us know which screen it is so we can assess if it's similar to what we are currently building! Thanks.
  13. Unfortunately, it's an architectural problem due to constraints in the underlying infrastructure, not a simple matter of adding a setting. One of the things we are working on this year is reworking a significant part of the infrastructure to give us more reliability, more scalability and - what matters in this case - more flexibility. Once we have that flexibility, we will start to explore what to do with it. -- ian
  14. My philosophy is pretty simple: get Evernote back on the path of developing and shipping quality software, use that as a foundation for accelerating customer-focussed innovation, and thereby put the company onto a sustainable growth trajectory - a trifecta that is ultimately the best combination of things that we can do for our users. All of our community knows that each of those is an undertaking - which makes it easy for me to be transparent with you all about the effort involved, and to involve you all in the process we're going through this year via the Behind the Scenes videos. As I said in January's blog post, we're going to make the product we all know and depend on more worthy of our ongoing affection, although I recognize that in navigating this process we're almost unavoidably going to disappoint some folks based on the places we focus and the choices we make. Our commitment to early beta testing, along with early disclosure of our direction through the videos, is helping us course correct and identify unanticipated challenges as early as possible in the process. Finally, the company continues to be on sound financial footing, getting even sounder this year. We're a private company, so it's relatively easy to throw a bunch of fud around concerning our financials, but two key facts speak for themselves: First, since the statement quoted above that Chris made in 2016, we haven't raised any venture funding. And second, we're still here. A rational interpretation of those easily confirmable facts, coupled with the observation in the New York Times article that I expect us to be profitable on an annual basis for the first time this year, would be that over that time we've been successful in managing our burn rate against cash reserves, and that we're now growing up into profitability. While I know that it's sometimes more entertaining to spin more elaborate theories, it really doesn't need to be - and more importantly, it isn't - any more complicated than that. I continue to appreciate the patience of every one of our users while we work to create a better Evernote, the Evernote that they deserve in return for their commitment. Back to lurking now.
  15. @RavBoy... always lurking. But also not inclined to make commitments until I know we are going to deliver on them. Trying to get us into the underpromise and overdeliver habit, which is harder than you might think! Right now we are 100% focussed on trying to make the existing Evernote we have work better, by stamping out bugs, unifying the codebase, and making the Evernote experience more coherent and more consistent across devices. Hence the focus of pretty much all the Behind the Scenes videos so far. That being said, let me take your specific question under advisement.
  • Create New...