Posted by david927 6/29/2025
Ask HN: What Are You Working On? (June 2025)
Plugin to convert Figma designs to React Native code fully client-side.
And a complimentary service that syncs the code directly to your filesystem in real-time, as well as an optional MCP server to flex the generated code to your codebase to fit your framework/libraries.
Source: https://github.com/kat-tax/figma-to-react-native
(includes cool tech like lightningcss-wasm for styles conversion and esbuild-wasm for client-side previews)
https://frottage.app/static/wallpaper-mobile-latest.jpg
https://frottage.app/static/wallpaper-desktop-latest.jpg
https://frottage.app/static/wallpaper-desktop-light-latest.j...
We just finished an android app, to set the wallpaper automatically on mobile: https://play.google.com/store/apps/details?id=com.frottage
I got the demo video produced, and a blog set up and seeded. You can see some of the science behind learning multiple languages at https://phrasing.app/blog/multiple-languages or follow my progress using Phrasing to learn 18+ languages at https://phrasing.app/blog/language-log-000
Now I’m working on the onboarding process, which I’m very excited about on both a product and a technical level. On the product level, it dovetails nicely into most of the shortcomings of the app. One solution to a dozen problems.
On the technical level, I’m starting to migrate away from reagent (ClojureScript react wrapper). The first step was adapting preact/signals-react to support r/atom, r/cursor, and r/reaction. This has worked beautifully so far and the whole module, with helpers, is less than 100 LoC. I’m irrationally excited about it, and every time I use any method it brings me a stupid amount of joy… especially since it’s exactly the same API as reagent.
For those curious, the next steps in the migration will be: upgrading to React 19 support once reagent ships with it (in alpha currently), then replacing the leaf components with hsx and working my way up the tree. No real code changes, just a lot of testing needed. Maybe at the end of it all, I can switch the whole app over to preact — will be interesting to test the performance differences.
As far as ideas I’m thinking about, I’m currently planning the next task in my head. This will be an (internal) clojure library that will hopefully have ClojErl (erlang), ClojureScript (js), and jank (C) interfaces, which means I’ll be able to write clojure once, and run on the server, browser, and mobile — all in their native environment. Needless to say, being able to write isomorphic clojure without running JavaScript everywhere has me almost as excited as my signals wrapper :D
For example, you can scroll through 60 pictures from my window https://stacks.camera/u/ben/89n1HJNT
Most of the challenges are around handling images & rendering, but I've also been playing with Passkey-only authentication which I'm finding really interesting.
Among other things, my team has implemented access-based sharing using web links, like Google Docs for real paper handwriting. And we've just launched Quin, our AI assistant for real paper handwriting. Super useful for getting help with math, language learning, looking up relevant facts, generating ideas, etc.
[2] https://lucassifoni.info/blog/leveraging-hot-code-loading-fo...
My 5th gap year (unemployed)
Turn any command into an AI-discoverable MCP tool with a few lines of YAML:
name: hello-world
description: "Greets the world"
command: "echo 'Hello, World"
Any AI agent can search for "greeting" and use your tool.
I'm also building the first registry at https://enact.tools