Tomek Czajecki

@satya164 Strong agree on all three. Sad that AI models default to this behavior. PR-description-shaped blob of text. Random stream of consciousness, listing all changes as if reviewer had no access/ability to understand the code.

For me, there are three main fails of AI-generated PRs: - The description is way too long and often repeats the diff (e.g., list of files and what changed in them) - Tests that check implementation and history (e.g., if a file were deleted, a test would check for the non-existence of the file) - Comments that explain the change instead of the code (e.g., this no longer does X, it now does Y) Takes more effort to read (most of the time I ignore half of the description), and then I need to clean up the tests, comments, and description before merging. Luckily, they are easily fixable: - Write a short, clear description of the "why". Include screenshots and videos when relevant. - Test public behavior, not implementation details or history. - Move the description of the change into the PR, keep comments focused on current behavior. If you do this, I already appreciate you 🫶

New look check this out

@peterpme @wcandillon WebGPU is a good API that reflects well how modern GPUs work, but it also means it's relatively low level and it can ONLY draw triangles. Rasterizing a path is tricky. Text is an incredibly hard topic. Skia is well thought and if you don't use it you end up reinventing it.

@wcandillon Would it be dumb to skip skia and use webgpu for complex charting directly?

We understand that people will use WebGPU via a third-party APIs such as TypeGPU, Redraw, Skia, Three.js, TensorFlow.js, you name it. That being said, if the lower-level API sounds interesting to you, I can only encourage you to dig in. This is an extremely elegant API developed by the most talented people in the industry. There is a fantastic in-depth publication at webgpufundamentals.org from Gregg Tavares that teaches the fundamentals from the ground up. @wa2goose has also made a great React Native WebGPU tutorial that walks you through the base concepts of the render pipeline: youtube.com/watch?v=vons_X…

@thekitze This is called Euro summer

can we just agree as human beings to not working during the summer, we can do this we have the technology

All GQL codegen on expo.dev is now using gql.tada. Amazing library!

@sethwebster @aleqsio @thymikee Can you call it a secret if it’s literally named FOUND-ation

@aleqsio @thymikee Yes. Definitely b

React Native has a new home now🎉

@hirbod @felippewick @cnakazawa fbtee is so good and works so well with Expo apps

@felippewick English first + German (if you have some confidence in the Berlin market) to start. Forgot about the rest. If you have PMF, add Spanish, Chinese, Hindi, and French. Use @cnakazawa library github.com/nkzw-tech/fbtee

With respect to cracking conversion funnel in my mobile app, should I put off localizing to as many countries as possible? Or go broad asap?

Amazing week. Was great to see everyone! If you missed it - here are some great pictures from @jmeistrich

In case you ever wondered how to scan that QR code with your Simulator 😉

@Baconbrix 🫡

After 9 years, I just finished my last week at Expo. Started working on it when I was 19, and it's been the center of my life ever since. Incredibly grateful to the team and community we built along the way!

This is such a good post. orchidfiles.com/im-tired-of-ai…

@grabbou @appjsconf 👋

This week in Krakow 🔜 @appjsconf Who's going there? 💣

It's App.js week again. Who is already in town?

@TesterArmy @expo Huge

We just rolled out official support for @expo EAS! Run your agentic E2E tests in the EAS pipeline ✨

@thymikee Exciting! My current biggest pain point with agent-device (or tbh anything that controls iOS sim) is how slow everything is

working on a faster boot, interactions, and test replay for agent-device. so far: → 3.4x faster than baseline → 1.5x faster than Maestro (yes, we're adding compatibility layer) shipping this in v0.15 once tested better

The moment you see claude calling git reflog and you know it's going to be a fun rest of the session

We just cut the SDK 56 beta 😅 ◆ 50%+ faster iOS builds (precompiled XCFrameworks) ◆ 40% faster cold starts on Android ◆ Expo UI is stable ◆ iOS widgets are stable ◆ expo-router rebuilt from scratch ◆ Inline native modules ◆ Brownfield multi-app support The obvious themes are speed and stability. But there are a lot of other interesting changes (like Expo Router decoupling itself form React Navigation). Get all the nuance and detail in the changelog below ↓

Just caught Claude trying to dump session tokens to an object passed around the whole web app. Ability to review PRs remains a competitive advantage.

@pariscestchiant @luciascarlet I was looking for something like this

i love SF symbols, but gosh i can NEVER find icons i want. there are 6k+ options, categories make no sense, and search is useless so i fixed it:

@tanishqk I "switched" to it when it became a default. Don't see much difference. It doesn't see to hit the plan usage limits faster and doesn't seem to be smarter/better in the things I use it for. Just more of the same.

Opus 4.7 is the first model update from Anthropic I haven't sprinted to turn on immediately. Haven't even tried it for coding yet. we must be plateauing. ill believe mythos when I see it (and even then, i bet the pricing will be ridiculous)