After the initial release, I’m not stopping with updates of Brain3k. Last day I added a cool new feature - an article summary created using @smmry_ API. Right now you are not one step away from seeing a page, you usually get what you are looking for from the app itself.

RT @paulbeusterien: Happy the @firebase open source process went well for you - @brain3k We appreciate your working through the issue and P….

Brain3k is available to download on App Store and Mac App Store! Change how you collect bookmarks to something more similar to your biological brain. Don't waste time managing links; type related text to find them. Visit to learn more.

Do you set your own 2022 goals? If you are curious about my results, please follow this profile. I'll be sending Brain3k updates and thoughts here. Happy New Year, and I wish you all that your 2022 goals came true 🍾🎆🤩.

3. Find a business partner. The cooperation of @ukutaht and @MarkoSaric is very inspiring (@PlausibleHQ). I'm pretty good at mobile development but preparing marketing materials (both design and copy) is hard. I hope to find a partner who will help me with marketing.

2. Gather the first 100 subscribers. With a generous free version (100 memories for free forever), seeing first paying subscribers may take some time, but it doesn't happen if nobody knows about the app. So I plan to focus more on marketing this year. Hence, the third point.

1. Release the application in January. The application is already in the state where it can be used (I'm using it myself for two months), but some things are missing. The most important one is the Landing page (work in progress).

I'm not going to lie. I had great expectations regarding this app, and I love using it myself, which was why I built it. Also, the possibilities for the following features are extensive, and I can wait to start implementing them. But what are my goals?.

The start of the new year is an excellent time for setting goals. @thepatwalls build a page where you can share your own (and win awesome rewards 👉 . It motivates me to set my own three goals related to Brain3k 👇.

So it turns out that is nothing to fear. My code is already merged to the master branch, and it will be released in January. Brain3k will work as expected on all platforms, and other developers will also be able to make their macOS apps with Firebase Auth.

Rosalyn, Nick, and Paul, developers from Google, are very friendly. They asked precise questions, gave hints on how to improve it, and were very responsive. They also mentioned an excellent job done in that PR, which was nice to hear.

I was a bit scared because Firebase is not a small library and many people rely on it. I wondered if maintainers would accept a PR from a developer from another side of the world. But my experience was fantastic.

What was that bug, you may ask? It was related to authentication from extensions on macOS. Brain3k will support iOS, iPadOS, and macOS, so offering the best experience on all platforms was critical. I did some digging, and I found a solution

When PR is accepted to the original library, everyone can enjoy a bug-free solution. I did that many times, but often PRs go to small libraries maintained by one person. This time I found an issue in the newly added feature of firebase-ios-sdk.

Most devs fork the library on GitHub, fix the issue, and start using their fork. It is not an optimal solution. If maintainers update the original library, they have to update their fork. It's better to fix an issue and create a Pull Request.

During software development, we face the situation when something isn't working daily. 99% is a fault of our code. But that 1% a third-party library or SDK is a culprit.

I fixed the macOS issue in the @Firebase Swift Open Source library. Here is my experience 👇.

The technology here is impressive, but the role of a responsible software developer is to pick the right technology for the problem, not the opposite.

To give you examples:.You don't need DAO to gather money. You don't need NFT to sell rights to digital art. You don't need a blockchain to run the Kickstarter platform.

But it should work like this:.👍 There is a problem, so you use technology to solve it. Not the opposite:.👎 You are trying to use technology on non-existing or already solved problems.