When choosing applications, if using or migrating your data between applications is important to you, look for one or more of these features:

• Drag-and-drop
• Export functions, especially to PDF or text formats like rich text or Markdown
• File Provider support, e.g., access via Files.app, on mobile
• AppleScript support on the Mac, Shortcut support on mobile

But be aware, some applications implement proprietary variations of commonly used functions, like their own flavor of Markdown. Or perhaps they store document metadata in a particular way or location, making it difficult (or impossible) for other application’s to use it. These things may be overcome using other tools, like scripting, but there’s no guarantee it can be done. Apps using standards lead to more opportunities.

In general, reinstallation should not be one of your first steps. This is especially true when it’s a non-fatal issue, e.g., it’s not crashing. Reinstalling rarely resolves an issue and usually does nothing more than remove information important in troubleshooting. Instead go to our support resources or contact our support team directly.

If you are working with out support team and an issue persists beyond deeper troubleshooting, we may suggest to reinstall the application but we will provide proper per-application instructions, as needed.

While running the latest operating system can be exciting, we suggest not installing the first release. Waiting for the first or second revision is a good idea. However, once you have it installed, we recommend you stay current with the point releases to ensure you have the latest fixes.

Regarding beta operating systems offered by Apple, we strongly suggest you do not install a beta operating system on a production or mission-critical machine. Betas can, and often will, break things that worked previously and also introduce new issues that can manifest in a variety of forms.

Be aware, there is no 100% bullet-proof clipping solution in any application. Dynamic variables, like network quality, reachability and responsiveness of remote servers, bandwidth throttling, etc., can effect whether content can be successfully clipped. When the clipping mechanism encounters an unresolvable issue, a bookmark is clipped so there’s at least something useful captured. Trying the capture again may produce the desired result.

We are a very small team and software development is a dynamic environment. Unforeseen challenges can pop up out of nowhere and external and internal factors can change priorities while we work on a new release. Therefore we do not publish roadmaps or timeframes that we might not be able to meet.

• Applications are independently developed so features and functions in one aren’t necessarily going to be in another. And the vision and focus of each development team may not lead them to implementing the same features as other apps.
• Some features aren’t technically feasible to implement. Also, one developer may use proprietary code to add a feature, so reproducing it in another app may not be easily done.
• Not every feature makes sense in every application, for example it would of course be technically possible to add podcasting features to DEVONthink To Go but it’s far outside the focus of the app.

However, we always listen to and assess politely made suggestions.