{"id":28785,"date":"2023-07-18T10:00:45","date_gmt":"2023-07-18T17:00:45","guid":{"rendered":"https:\/\/www.podfeet.com\/blog\/?p=28785"},"modified":"2023-07-19T16:12:11","modified_gmt":"2023-07-19T23:12:11","slug":"bear-2","status":"publish","type":"post","link":"https:\/\/www.podfeet.com\/blog\/2023\/07\/bear-2\/","title":{"rendered":"Bear 2.0 is Even More Beautiful and Packed with New Features"},"content":{"rendered":"

<\/p>\n

\"Bear
<\/figcaption><\/figure>\n

<\/a>Just a bit over six months ago, I told you why I replaced the Note-taking\/organizing app Ulysses with Bear from bear.app<\/a>. Don\u2019t worry, I\u2019m not abandoning it for something newer and shinier, I\u2019m here to sing the praises of Bear 2.0 which was just released.<\/p>\n

As you may recall, I chose Bear out of a host of other options because it has a simple yet elegant design, it syncs across my Mac, iPhone, and iPad, and most importantly supports TextExpander on all of those devices. The price of $15\/year made it less than half of all the other contenders. Now I\u2019m not sure when it changed, but the price is now $30\/year for the Pro version<\/a>, but they do still have a free version with some limitations. While $30 is double what I was paying, the price is still under the competitors I tested such as Ulysses at $40, Craft at $60, and Obsidian at $120\/year.<\/p>\n

Bear was already clean and elegant, but somehow they have managed to make Bear 2.0 even cleaner and more elegant. I\u2019m not sure how to quantify it, but everything is prettier. The new version isn’t just a new paint job, they’ve added and improved a lot of features.<\/p>\n

Feature Improvements<\/h3>\n

I don\u2019t normally read release notes, but when I heard that Bear 2.0 was released, I wanted to learn about every new feature. I won\u2019t go through every feature in detail but I do want to talk about the improvements that blew my dress up.<\/p>\n

Bear is a great app for writing in Markdown, the simplified, plain-text way to write for the web. If you’re not a Markdown user, Bear is still a great way to write in plain text, but I’ll be focussing a bit here on using Markdown with Bear.<\/p>\n

Markdown is great because instead of giant gloppy HTML syntax like \u201ca href\u201d and weird brackets and such for URLs, you just put the text you want people to see in square brackets, followed by the URL in roundy brackets. It\u2019s much more readable and less distracting for you when you\u2019re typing and if anyone else needs to read it later it\u2019s cleaner for them too.<\/p>\n

Tables<\/h3>\n

Tables are incredibly annoying to create and read in HTML. While they\u2019re much simpler in Markdown, they\u2019re still difficult to type. It\u2019s a lot of pipes and dashes and colons to designate title cells and justification of text inside the tables. I usually Google for a Markdown table generator website whenever I need to make one.<\/p>\n

With Bear 2.0, they added a button to create tables. It creates a two-column, two-row table with the first row being a heading. Hovering over any of the cells gives you a slew of options to add more rows, and columns, and to change the text justification for the column. Bear also formats it into a pretty table while you\u2019re working, but when you export the table it\u2019s the full Markdown syntax so you can use it on the web.<\/p>\n\n\n\n\n\n
This is a Title<\/th>\n\u2018Nother One Title<\/th>\n<\/tr>\n<\/thead>\n
Right-justified<\/td>\nCenter-justified<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

You have to have lived through typing in tables by hand to appreciate this enhancement, but you can expect to see more tables in my blog posts now.<\/p>\n

Markdown Hiding<\/h3>\n

While Markdown is much more pleasant to look at than HTML when you\u2019re writing, even Markdown is a bit distracting. For example, the level of your heading is designated with the same number of hashes, so a Heading Level 1 would be one hash, and Heading Level 2 is two hashes. In Bear 1, if you put one hash before a title, it would show \u201cH1\u201d to the left.<\/p>\n

Not super ugly and intrusive, but Bear 2 gives you the option of hiding your Markdown, so you just see a big, bold title for Heading Level 1 and a slightly smaller version for Heading Level 2. The nifty way they did this is that if you click in the heading, the Markdown reapears so you can easily change it.<\/p>\n

With Markdown hiding, linked text to URLs just shows the text in red with a little pencil next to it instead of the full Markdown. It\u2019s just beautiful.<\/p>\n

The new fad in URLs these days is to have link previews – a rich media thumbnail of the linked website. Apple Mail added it recently and I think it works really well to give people context for URLs in emails. Bear 2 adds the linked preview option too. For my needs in writing blog posts, I don\u2019t really need the feature but it\u2019s a setting so everyone can see their links the way they want them.<\/p>\n

All the Fonts<\/h3>\n

For some reason, Bear used to only have 6 fonts to choose from. To be fair, it\u2019s a plain-text editor so why do you need all those fancy fonts? Well, because we like fonts, ok? That\u2019s the only justification I can think of. The good news is that Bear 2 now allows you to choose from all of the system fonts.<\/p>\n

The other nice thing about Bear 2 is that it gives you different fonts for text, headings, and for embedded code snippets. That last one might not be interesting for normal people but a lot of NosillaCastaways write code and it\u2019s super nice to see it in a font that makes you happy.<\/p>\n

For the same reason people like fonts, people like themes. Bear 2 adds six new themes to their library, bringing the total to 28 if my cipherin\u2019 is correct.<\/p>\n

Images<\/h3>\n

I only embed images into my Bear documents as placeholders because I like to do fancy-pants things with my images for my blog posts. I use a big ol\u2019 pile of HTML and styles Helma helped me create to make them look nice. I define the exact size in pixels, I make them part of what\u2019s called a Figure, with a nice little border around them and a title that\u2019s in italics.<\/p>\n

But if you like to put images in what you write in Bear, you\u2019ll be happy to know that you can now crop and resize images in the app after you\u2019ve placed them. If you click on an image you\u2019ve placed, you\u2019ll see a little triangle with dots on it in the corner. If you drag the image, it resizes. Now I said you can crop images too, but for the life of me in all of my testing with holding down Option, Shift, Command, and Control, I haven\u2019t figured out how to drag to crop an image. I\u2019m sure it works, but even referring to their support pages I can\u2019t figure it out.<\/p>\n

Search Images<\/h3>\n

Bear 2 added the ability to actually search in images. I know that’s becoming commonplace but it tickled me when I tested it.<\/p>\n

Formatting Stuff<\/h3>\n

In Bear 1, if you hovered over the bottom right of the window, a quill pen icon would magically appear. Selecting the quill would reveal a list of formatting things you could do and their corresponding keyboard shortcuts. From heading levels to bold\/italics\/underline to different kinds of lists and code blocks, it would all show in this popup menu. But when you let go of the popup menu, it was gone, and so was the quill.<\/p>\n

Bear 2 makes it ever so much easier to discover and use the formatting options. If you move your cursor anywhere on screen, at the top of every window, you\u2019ll see a button that says BIU for Bold, Italics, and Underline. If you select the BIU button, a formatting bar appears at the bottom of the screen. It\u2019s the same information we saw in the popup for Bear 2, but I really like having it visible, especially because it has the button to embed a table.<\/p>\n

\"Bear
Bear 2 Formatting Bar<\/figcaption><\/figure>\n

If you’re a VoiceOver user, don’t upgrade to 2.0<\/h3>\n

As I was playing with this feature, it occurred to me to test Bear in VoiceOver on the Mac. I’m afraid it’s a hot mess. I couldn’t find a single button that was labeled, so they all say “button”. Navigating to the list view of notes, it didn’t even read them.<\/p>\n

I switched to the iPad hoping that it would work better, but I was soon disappointed. Unlabeled buttons weren’t the worst of it, it actually read things out incorrectly. For example, when I select an article, instead of reading it, it reads me the name of embedded images and PDFs.<\/p>\n

In my recent article How I Test Apps for Accessibility with VoiceOver<\/a>, I explained that when I find an app that isn’t accessible, I send feedback to the developer in hopes of prodding them to do better.<\/p>\n

I wrote to the folks at Shiny Frog, makers of Bear, telling them that I’m in love with 2.0 but that I want all<\/em> of my friends to be able to enjoy it. Konstantin wrote back 17 minutes<\/em> later with this response.<\/p>\n

\n Thank you so much for your support and love.<\/p>\n

You are totally right. While the first release of Bear was fully functional with VoiceOver, version 2.0 lacks this support. Unfortunately, we couldn\u2019t test Bear for VoiceOver before the 2.0, simply because of lack of time.<\/p>\n

Full VoiceOver support is indeed planned and will be integrated as soon as the launch bugs are all squashed. I will personally take care of this.<\/p>\n

We always strive to have the most accessible App possible, and I must confess that I feel ashamed of the current lack of VoiceOver.\n<\/p><\/blockquote>\n

I told you in my article that I almost always get a good response from developers, and here’s proof of this. While ideally VoiceOver support built into the release would have been a better decision, this response comes in a very close second. If you’re a VoiceOver user and you’re using Bear 1, don’t upgrade to version 2. I verified with Konstantin that you cannot downgrade from Bear 2 to Bear 1.<\/p>\n

Info Pane<\/h3>\n

One of the features I really like about Bear is that it tells me how long it will take to read an article. This is important to you as one of the listeners to the NosillaCast because it\u2019s how I gauge whether I\u2019ve created enough content for you for the week. I\u2019ve never gotten a complaint about the show being too long, but I have heard a comment here and there if the show is too short!<\/p>\n

The Info pane in the upper right of the Bear 2 window shows the identical information as it did in Bear 1, but it\u2019s ever so much more readable. This is a really good example of what I said at the beginning of this article – it\u2019s more visually pleasing. It still shows me the number of words, characters, paragraphs, and read time in my article, but in Bear 2 each piece of information is in this nice rounded rectangle box making it somehow clearer and easier to read.<\/p>\n

\n
\"Bear
Bear 1 Info Pane<\/figcaption><\/figure>\n
\"Bear
Improved Bear 2 Info Pane<\/figcaption><\/figure>\n<\/div>\n

In my usual method of poking things to see what they do, I figured out that if you poke one of these statistics, like read time, it keeps the read time in a little box at the bottom of the window next to the formatting bar. I think it\u2019s probably a really bad idea to constantly be watching these stats as you write, but I do like having instant access to the information.<\/p>\n

\"Floating
Floating Table of Contents<\/figcaption><\/figure>\n

The info panel in the new version of Bear has two new tabs. If you write with headings as I\u2019ve described, you get a sweet table of contents. I say sweet, because not only does it show you each of your headings, you can click on a heading and jump right to it in your document. An interactive table of contents can really help when working on a long-form document.<\/p>\n

As a reminder, one of the really good reasons to use headings as a semantic element for your text is that this is how our screen reader friends can more easily navigate a web page. Just making the text big and bold doesn\u2019t help them navigate at all.<\/p>\n

Speaking of headings, Bear 2 lets you fold up heading sections so it\u2019s easier to scroll through your document. As an example, if I click on the heading for Search Images in this article, I can see the Heading Level 3 icon, and a right-click on that lets me choose to fold it up.<\/p>\n

When I choose to fold this heading, it shows three dots to the right so I know that\u2019s a folded section. I can tap the 3 dots and it folds back open. You can also choose to fold up all sections which can make it super efficient to jump to one section and get to work.<\/p>\n

The one thing I discovered the hard way is that if you export the Markdown text while any sections are folded up, you’ll get some Markdown glop for that section in the export.<\/p>\n

\"Search
Search Images Unfolded<\/figcaption><\/figure>\n
\"Search
Search Images Folded Up<\/figcaption><\/figure>\n
\"All
All Headings Folded Except Title<\/figcaption><\/figure>\n

Footnotes<\/h3>\n

If you\u2019re a serious writer, you can now add Footnotes in Bear 2. It\u2019s super easy. Set your cursor where you want the footnote to be, click the 3-dot menu in the formatting bar at the bottom of the Bear window, and select Footnote. You\u2019ll see the Markdown syntax for a footnote which is pair of square brackets enclosing a caret symbol and the number for the footnote. At the same time it inserts that footnote annotation, it puts the same annotation at the bottom of your Bear note with placeholder text that says \u201cfootnote text\u201d.<\/p>\n

I\u2019d never done a footnote on a web page before, so I tested it, and sure enough, it works!<\/p>\n

\"Footnote
Footnote Annotation in Markdown<\/figcaption><\/figure>\n

App Icons<\/h3>\n

Along with people caring about fonts and themes, people seem to really like changing their app icons. Bear 2 comes with 15 different options – one of which is even an adorable rainbow bear.<\/p>\n

\"Bear
Bear App Icons<\/figcaption><\/figure>\n

Bottom Line<\/h3>\n

The bottom line is that the upgrade to Bear 2 adds some really useful capabilities (and I haven\u2019t even told you about all of them!) They\u2019ve managed to take a clean and elegant interface and made it even cleaner, more elegant, and easier to use. The only caution I would give you on upgrading to Bear 2.0 is that you need to update all of your devices to the new version. Notes created or edited in Bear 1 will not sync to Bear 2 devices, leaving that device will be kind of frozen in time.<\/p>\n

If you want to get a feel for the playfulness and beauty that is Bear, go over to bear.app<\/a> and watch the delightful line art video they posted on the home page. It will bring you joy whether or not you decide to try the free or paid version of Bear. It’s gratifying to see that the money I’ve spent on my annual subscription is going towards all the great new features.<\/p>\n","protected":false},"excerpt":{"rendered":"

Just a bit over six months ago, I told you why I replaced the Note-taking\/organizing app Ulysses with Bear from bear.app. Don\u2019t worry, I\u2019m not abandoning it for something newer and shinier, I\u2019m here to sing the praises of Bear 2.0 which was just released. As you may recall, I chose Bear out of a […]<\/p>\n","protected":false},"author":1,"featured_media":28784,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[147],"tags":[5602,5967,5966,5603,2912,128],"class_list":["post-28785","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-posts","tag-bear","tag-bear-2","tag-bear-2-0","tag-bear-app","tag-note-taking","tag-notes"],"jetpack_featured_media_url":"https:\/\/www.podfeet.com\/blog\/wp-content\/uploads\/2023\/07\/Bear-App-Icons-1040x520-1.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/28785","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/comments?post=28785"}],"version-history":[{"count":11,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/28785\/revisions"}],"predecessor-version":[{"id":28855,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/28785\/revisions\/28855"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/media\/28784"}],"wp:attachment":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/media?parent=28785"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/categories?post=28785"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/tags?post=28785"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}