No doubt writing in Bear (Panda) is a wonderful experience, unmatched by many note-taking apps. And using Panda to edit Obsidian notes works great if you don’t require auto-completion of tags or backlinks (e.g. using Panda for long-form or non-linkable content).
The big “risk” has to do with the incompatibility between many Obsidian features and Bear (Panda). So depending on which features you’re using in Obsidian, you may run into quite a bit of trouble if you are planning to eventually move all your Obsidian notes back into Bear 2.0 (Bear w/ Panda).
For instance, as of today, any Obsidian notes that use standard markdown images - e.g.
!(remote_image_path_url) - will not only not work in Panda, but will continue not working in Bear 2.0. I’d love to see Shiny Frog support remote images, but there are two reasons they may not do this: (1) it’s quite hard to implement in their custom editor. And (2) it could potentially hinder their business model.
Tags and standard backlinks in Obsidian (regular note-to-note links) will port just fine into Bear 2.0. However, backlinks to paragraphs within notes (ie. transcluded blocks) or even links to headings within notes will not work in Bear. At least, not until Shiny Frog implements a custom Obsidian importer that parses Obsidian’s custom referencing schema.
Any embedded PDFs, which function beautifully in Obsidian, will not in Bear/Panda (other than as a clickable link to an external PDF file). And ditto for any embedded Youtube clips, which again, function just fine in Obsidian but will simply appear as a non-clickable html embed in Bear/Panda.
But if you have no need for embedded images, PDFs, or video clips within your notes, and you’re only using standard note-to-note links - then you should have no issue using Panda today to edit your Obsidian notes (or any other .md files) and Bear 2.0 once it’s ready.