mhammerc

We use MCP in our monitoring systems.

A claude routine runs without access to internet except for Slack (API) and Sentry (MCP).

It reads the Sentry MCP, compare the errors to the app source code and post a daily digest to Slack.

The reports are very accurate.

As an example, I have ~/Library/Android/sdk which takes 8 Go.

If I know I do not need the Android SDK, I can safely delete it.

Yes!

You can go to the folder ~/Library and then delete what you want.

To open the folder from a terminal: cd ~/Library open .

In the Finder, you can enable "Calculate all sizes" from "View options," which will calculate folder sizes to understand what to clean first.

This folder contains data from all apps; sometimes it is cache, sometimes persistent data. You will find all your previous apps taking gigabytes...

I run Arq Backup automatically in the background.

It copy Photos, iCloud files and my mails once every days to S3 with incremental backups.

It requires to have a full copy locally.

Works great!

It is not hard to configure once, with the proper folders and settings.

I have been working for the past four years exclusively on react-native apps and their backend API, from bootstrap to publishing, adding new features every few months and maintaining the apps.

It was a mixed experience. When I migrated to expo two years ago, many problems were solved but not all.

But I still encounters bugs and problems with many common dependencies. It is not uncommon to have bugs on certain Android brands, with the community on github reporting the bug but waiting months for it to be fixed.

iOS is by far better and more stable than Android.

Performance is great on iOS, but less great on Android.

Our apps are animation heavy using react-native-reanimated and react-native-skia. Everything went perfect on iOS but we had to remove some animations or simplify them on Android.

Upgrading your dependencies every four months will probably break something somewhere : deep links stop working, some animations stop working, or maybe it's another dependency from the JS world. Sometime the fix is easy, other time an issue with the regression can be found on Github, other time we have no data.

Overall I'd say react-native is perfectly servicable and is easy to learn for anyone, which is a big plus. I'd recommend react-native because it is easy, have a big JS ecosystem, but I am now on the Flutter side.

App: Expo, React-Native, Typescript, Apollo Client

Server: Node.js, GraphQL, TypeGraphql, Apollo Server, PostgresQL 14, Redis

Website: Webflow (great for a good website with minimal work)

Hosting: Digital Ocean (it’s cheap but I prefer GCP)

Internal tools: Retool

I had good times with Opus.

We have been capturing then encoding audio using Opus from a low-power chip (nRF52840) then sent encoded data through BLE.

Worked liked a charm! Encoding used 50% of the CPU time.

I can relate, I broke my MBP16 screen because of a camera cover. Apple repaired my mac for free without a hitch.