If you've built an Android app that runs on an emulator, that's great.
But there's a lot more to getting it in people's hands: release builds, signing keys, store listings, and much more.
In this handbook, Nikheel walks you through the whole process so you know what a production release takes.
https://t.co/VJs1DDaeuj
@simonschubert hi @simonschubert is there any option to remove the 1st placeholder page for 'face' (a face of your own) and the last placeholder page for 'widget' (no widget on this page...) that would make the pages look so clean
Introducing Pixel - a library for building GUIs in the terminal
- 120 FPS pixel-perfect graphics
- Embeddable inside existing TUIs
- Built in chromium webview component
https://t.co/rZJ6lyHgJD
I used Reverse Engineer Anything to re-create raycast on @omarchy. And I was blown away! In just a couple hours I have a fully-functioning raycast-like launcher! Right now it:
* Learns your habits
* Apps + every Omarchy action in one search
* Aliases & favorites
* Keyboard-first
* Follows your Omarchy theme live, opens in ~40ms
repo: https://t.co/adlqEYGFry
Most developers accept the very first code solution an AI gives them.
Boris Cherny (the creator of Claude Code at Anthropic) shared the exact prompts their internal engineering team uses to force better output:
1. The "Elegant Rewrite" Prompt:
When the AI gives you a messy, band-aid fix that technically works, reply with:
"Knowing everything you know now, scrap this and implement the elegant solution."
2. The "Reverse PR Review" Prompt:
Before opening a Pull Request, flip the roles and make the AI test you:
"Grill me on these changes and don't make a PR until I pass your test."
3. The "Behavioral Proof" Prompt:
Instead of asking "Does this work?", say:
"Prove to me this works by diffing the behavior between main and this feature branch."
Stop treating coding agents like autocomplete.
Push them like a senior engineer reviewing a draft.
I am so much more exhausted when I program with AI than without it. I reflected a bit, and I think I know why.
First, I think about how to solve a problem. This step is the same with and without AI. Then, with AI I have to write a prompt with a decent bit of precision and somewhat more long-term than if I just jumped into straight implementing it and figuring out the details as I go.
Then you start up the agent, and you immediately have some other work to do and you jump to another prompt for another task, where you also think really hard and try to formulate what you want quite well.
By the time you're done, first agent has some code for you to review, and you can't slack - you need to actually review it and be diligent about it. And when you're done - second task is there for your review. So really there's not time to rest.
When I program manually, I can decompress while typing the code in, I can rely on my muscle memory for typing and navigating the codebase, so there's periods of deep think and some relaxation. With AI, there's only deep think. And as soon as you try to think less - you open the doors for slop.
It's so tiring.
If you have a full-stack app in your local environment and are ready to take it to production, this course is for you.
You'll learn about container orchestration, managing environments with Docker Compose, & deployment.
Along the way, Gavin also teaches you about working with Dockerfiles, testing your app, and more.
https://t.co/rYCld1SC6P
@derekmross An iPad with an M1 chip or newer (iPad Pro 2021 or later, iPad Air 2022 or later), on iPadOS 17 or later. 8 GB of memory or more is best for VS Code.
For every day I don’t launch the next things I’ll be giving everyone a r̶e̶s̶e̶t̶ OSS library, first up:
react-native-gpui
https://t.co/3sk0PyV6Ka
- Real Mac scroll physics: AppKit momentum + rubberbanding with Metal scroll-blitting at 120Hz
- Off-thread Reanimated: 2nd JS runtime with shared memory
- Paint-patch frames: In-place GPU opcode patching so animations don't trigger whole-tree redraws (50% → 2% CPU)
- Single native binary: Embedded JavaScriptCore, ~135ms cold boot
- Custom Metal shaders: Hardware-accelerated CSS transforms, rounded masks, and proper shadow clipping
Apple says you need a Mac to build iPhone apps.
Today I built one on Omarchy Linux, submitted it to the App Store, installed it on my iPhone over USB, and stopped it at a breakpoint in the debugger.
No Mac anywhere.
It's all open source:
https://t.co/ETOnP3n3X3
xtool is an open-source, cross-platform alternative to Xcode that can build and deploy iOS apps from Linux, Windows and macOS.
It builds Swift packages into iOS apps, then signs and installs them, and it can interact with Apple Developer Services from code. It runs on Linux, Windows through WSL, and macOS, and it is released under the MIT license.
Repo: https://t.co/8bgf9an54E
@TheFifeDawg@gladimdim@simonschubert While waiting for more Android permission support, I asked the agent to build a companion Android app as a bridge; via this, the Omarchy widget can get access to more Android APIs through the bridge.
@therealZpoint@derekmross It's just an android launcher, so basically you still have full working android plus proot Linux ability. give it a try in playstore, omalauncher.
@simonschubert@nowaytray Can we support more Android permission acquisitions? I see it only has limited notification support. It would be nice if we allowed all permissions for the freedom to build widgets.