Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Started using React Native two days ago and immediately fell down a tab-bar rabbit hole. I’d seen Instagram and Revolut collapse their tab bars on scroll while keeping every icon visible. I wanted that without giving up real iOS Liquid Glass. Turns out iOS 26’s public API can’t express...

67,945 Aufrufe • vor 2 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

And now, the recipe for the room-temperature glass layer… although unfortunately, you probably won’t get very far with it. The reason I haven’t shared the recipe until now is because I wanted to keep the Nobel Prize all to myself. NO. It’s because I spent the last two weeks trying to eliminate one component from the equation — a component that is almost certainly not something the average modern household has lying around. But now I’m going on vacation 🏝️, and obviously I’m not taking my labs with me. I’m not going to continue the experiments, I won’t be posting either, so it’s going to look as if I’ve simply disappeared. “Look, the guy tricked us and then disappeared without a trace!” Well, no. The result is real, the recipe is simple — you just probably won’t have the starting material you need. And despite struggling with this for two weeks, I couldn’t find a substitute for it. But maybe you will! 👍🏻 So I’m sharing the recipe as I currently know it, exactly as it is, in case someone can take it further while I’m sitting on a beach getting a tan. All I ask is that if someone manages to completely solve this mystery while I’m away, please consider a shared Nobel Prize! 🤪 So, the “secret ingredient” is none other than old, completely whitened, end-of-life waterglass. Yep. The stone shown in the video is proof that the glass layer is actually a precipitation. The layer is present on one side of the stone, but completely absent on the other side, even though the stone was standing vertically in the solution. Don’t let the visibly rough condition of the glass layer fool you — this was the first one, and I subjected it to all kinds of tests - too early. The important thing is that there is glass on one side, and ABSOLUTELY NONE on the other, even though the stone was standing vertically in the solution! So this isn’t the bottom and the top of the stone. It’s the right and left sides. Yeah. The glass is indeed a preipitated layer. So let me explain in detail what I did the first time I got this result. This stone was cast in that sour cream container (so it is an artificial one), and then I cut it in half with an angle grinder because I wanted to see what was inside. The inside was quite crumbly, so I decided to strengthen it. I soaked it in this, then that, then something else, impregnated it with one thing and then another, thinking that eventually it would become stronger. And while doing all this, I dipped the stone into all kinds of things. Ash lye, wine, waterglass, God knows what else. At this point, it doesn’t really matter. The funny thing is that now, having reconstructed what actually happened, I wasn’t trying to create a glass layer at all. I was simply trying to strengthen a crumbly stone. But there wasn’t enough waterglass in the lab to completely cover the stone standing in the container. Fill up with water? Nooo! I didn’t want to dilute it with water, so I started looking around in the cupboard and found a bottle of waterglass that was more than a year old and had already turned completely white. I poured this waterglass into the container on ONE SIDE of the stone. And I really mean one side. I did NOT mix it. I thought the waterglass will be "smart enough" to mix its old self with its new self. But the old one didn’t flow around to the other side. It simply accumulated against this curved surface of the stone and deposited there. The best evidence that this is exactly what happened is that even toward the edge of the curved section, the layer wasn’t nearly as thick as it was where I actually poured the old waterglass. And on the cut side of the stone, where I DID NOT pour any old waterglass, absolutely nothing was deposited. And this old waterglass is the thing you probably don’t have at home. Because modern people simply throw this stuff away. “It’s gone bad. Into the trash.” I spent the last couple of weeks trying to find an alternative solution that doesn’t require this old waterglass. Exactly so that I could start public beta testing. I didn’t want to release a recipe that would require you to wait an entire year to have one of the ingredients before you could even start experimenting with it. So I tried artificially aging the waterglass using all sorts of methods — baking soda, acids, slaked lime, carbon dioxide — but none of them produced suspended particles in the waterglass. So far, only waiting did. I did, however, lose a SodaStream machine in the process. RIP. 🪦 So, for now, the answer seems to be: either wait a year, or find some old waterglass in your cupboard. I haven’t found another way. Over the past few weeks, a few people volunteered to beta-test the process. But I only chose people who have been working with me for a long time, so there was at least a chance that they might have some old waterglass, or artificial stone, or both, at home. Mondo Mondo in Australia actually did the experiment, and it worked. I don’t know the Canadian guy, Odhinn , so I have absolutely no idea how he did it. Mondo’s waterglass wasn’t completely white, but it was thicker than normal — 46% from the shop — and it was at least six months old. Bingo. The experiment worked for him. What’s interesting is that once I finally identified the old waterglass as the responsible component, I tried using it directly — just soaking stones in the old waterglass by itself. And that didn’t work 😵 The important thing is (?) the mixture and ratio of fresh and old waterglass. Something like two-thirds fresh waterglass and one-third completely whitened, old waterglass. The explanation may be the following — and this isn’t me saying it, it's Mr. Grok: "The old waterglass provides the amorphous silica nuclei that are essential for the precipitation, while the fresh waterglass provides the chemical activity and high pH that keep the whole process going." Okay! There’s one more thing I need to add. I was only able to create really thick precipitated layers on artificial stones. All the other thick layers, such as the ones on granite or eggshell, were not precipitation. Those were simply the thickened sludge that had formed, which I then smeared onto the surface. Because when an artificial stone is dipped into the magical mixture, it somehow thickens the entire mixture. Even in the last experiment, when I thought the egg was responsible for thickening the magical mixture, there was actually a small piece of artificial stone sitting in the corner of the container. From there, suspicious brownish streams were spreading in every direction. In other words, the artificial stone was releasing something that caused the entire mixture to turn into a gel. So, that’s where we are right now. Feel free to experiment. As far as I know, apart from the half-dead waterglass, I haven’t found another method that works. And now, my flight is about to leave. ✈️

Marcell Fóti 🪨

21,406 Aufrufe • vor 1 Monat

opus 5.5 is f*cking cracked at motion design this entire video is code, 0 after effects im open sourcing the prompt template for these motion designs steal it to recreate these ↓ Ask me for: 8 to 12 UI states I want the shape to become (e.g. button, loader, player, slider, toggle, tabs, chart, command palette, toast), pure black and white or one accent color, and a royalty-free song around 120 BPM (e.g. Mixkit, free for commercial use). Dribbble-level UI motion. One shape, never cut: every state is the same element morphing its size, radius and color while its content swaps with a short blur. A cursor drives every change with real clicks and drags. Light warm-gray canvas, black and white components, one clean UI font (Geist). Springs everywhere, a tiny overshoot at most. The camera zooms so each state fills the frame. The last frame is the first frame, so it loops. Banned: bouncy easing, particle bursts, glows, gradients on UI chrome, mismatched icon strokes, dead time, anything that looks like a template. 120 BPM, 7 bars, something happens on every beat. Button → loader → check → dynamic island → music player with a play/pause morph → scrub the progress bar → it becomes a volume slider that stretches when dragged past max → a toggle flips on the beat → the knob becomes a liquid tab indicator → the tabs open into a chart that draws itself, with a tooltip on hover → it collapses into ⌘K → type to filter → enter → toast → back to the button. 1. One HTML file, square 1440x1440. Every style is computed from time inside seek(t): no CSS transitions, no timers, no state carried between frames. 2. Springs are closed-form step responses. A value that changes target many times is the sum of one spring per change, so it stays a pure function of time. 3. The tab indicator's two edges ride different springs, so the leading edge stretches ahead of the trailing one. Same trick for the toggle knob. 4. Drags are direct manipulation: while the cursor is held, the value is computed from its position. On release it springs back from wherever it was. 5. Analyze the song with numpy for the beat grid and start on a downbeat. Place every UI sound by its measured peak. 6. Render with Playwright: 4 subframes per frame, blended with ffmpeg tmix for motion blur at 60fps. 7. Render one frame per beat before the full render. Fix anything off the grid, cramped or hard to read. Never put will-change on anything the camera scales or the text renders blurry. Text that swaps inside a morphing container needs its own enter and exit timing or it overlaps. Make the last frame identical to the first, cursor position and speed included, or the loop stutters. Ask me for the inputs, then show me the state list on the beat grid before you write any code.

zero

1,130,310 Aufrufe • vor 13 Tagen

Reading the comments on this post told me everything I need to know about art. So many of you wrote to say you felt the exact same thing I did standing in front of the Starry Night. That strange pull, the sense that the painting is somehow alive... It turns out the feeling is completely universal. I am not someone who gets emotional easily. But every so often a piece of art really gets to me. And that is exactly what happened the first time i walked up to Van Gogh's magnum opus. I know how that sounds, it is one of the most famous paintings on earth, almost a cliché to be moved by it. But maybe it is that famous for a reason... It genuinely looks like it is moving while you stand there, shifting in a way I cannot explain and have never seen in any of the thousands of paintings I have looked at in my life. The same day I took the photo below, I also filmed this short video. It still comes nowhere near the real thing, but you can at least catch a little more of it here, the thick ridges of paint, the way the stars and swirls lift right off the canvas. This technique is called "impasto", from the Italian for mixture. It means paint laid on so thickly that every brushstroke and ridge stays visible on the surface. Van Gogh piled it on with a loaded brush, building the stars up thick so they would blaze as bright as possible against the dark. But no video and no explanation of technique can really convey what it feels like to stand in front of it. And the fact that so many of you felt the very same thing says something true about what art is really for. Tolstoy said it best: "The receiver of a true artistic impression is so united to the artist that he feels as if the work were his own and not someone else’s, as if what it expresses were just what he had long been wishing to express. A real work of art destroys, in the consciousness of the receiver, the separation between himself and the artist. In this uniting of it with others lies the great attractive force of art."

James Lucas

57,859 Aufrufe • vor 29 Tagen

sorry, they just did WHAT someone gave a machine one disease name, the leading cause of blindness in the developed world with 1.5 million americans already in its path, and it came back pointing at a drug that has sat in pharmacies for years under a different label: 551 papers read in 30 minutes against the 294 hours a human would have needed, and the loop that did it is public on GitHub most agent setups answer one question at a time, so the ceiling on the work is the quality of the question you happened to think of this one was handed a single question and wrote the second one itself. turns out that follow-up is where the real find was: a target called ABCA1, upregulated threefold, in an experiment no human ordered i read the whole paper looking for the trick, and the trick is structural. that is the second question, and it is the gap between an assistant and a factory: - hand the loop a field rather than a task: it was given a disease, and choosing the mechanism was part of its job - make it rank before it spends: 151 papers in, ten candidate mechanisms out, scored against each other before anything touched a bench - split reading from judging, so the agent that forms the theory is a different agent from the one grading it - close every cycle on physical reality: the verdict was an experiment, and another model's opinion was never allowed to stand in for one - feed each result back as the next question rather than a log line, which is the step almost nobody builds - search what already passed inspection first: the winner was an approved compound with a safety file already on record - write down what the round learned before opening the next one, so round two starts where round one stopped my read, and i think it is the uncomfortable one: reading was the entire bottleneck in that field, and everybody spent the decade optimising the writing. people ran every physical experiment here, the analysis agent needs a domain expert writing its prompts, and the authors decline to call this the leap it resembles. the thinking got replaced, and the hands did not so the question i cannot answer for my own setup: which step of your loop still stops dead until you sit down and type something bookmark this one. the four parts that turn one model into a line that runs like this, the queue, the rooms, the write permissions and the gate, are built file by file in the piece below ↓

Argona

32,744 Aufrufe • vor 2 Monaten

The gold standard fluid interactions on iOS are built using in-process client animations (like SwiftUI does it) and not render-server animations (like CoreAnimation does it). This is common knowledge inside of Apple’s UI framework and system experience teams. A close inspection of iOS’s evolution reveals the gradual upgrading of system experiences written using render-server animations (that often disable user interaction) with ones using client animations (that are interruptible and interactive). The app switcher for iPhone X, the Dynamic Island, and Liquid Glass bars are prime examples of this trend. The other thing that makes these experiences feel so fluid is their use of spring animations that preserve velocity, rather than Bézier curve easing functions. To get velocity preservation, you need to be able to interrupt a spring animation and retarget it or drive it with a gesture. That’s a lot easier to do when the animation is running in the same process as the event handling. When we were first pitching SwiftUI, two of our go-to demos were a recreation of the iOS 9 navigation and Home Screen interactions which were fully interactive and interruptible, at a time when the actual implementations of those experiences in the OS disabled user interaction and ran server-side animations. CoreAnimation is great and the framework does much more than animation. You can build a fine app using its server-side animations. But if your UI framework can’t do efficient main thread client animations, there’s a ceiling to the quality of the experience your app can provide.

Kyle Macomber

194,252 Aufrufe • vor 21 Tagen

I just built a Meta Ads diagnostic in Claude Code that tells you WHY your account broke, not just what changed 🤯 It spins up a team of agents that each investigate a different reason performance dropped, then argue against each other to kill the wrong answer before it ever reaches you. All inside Claude Code. Perfect for DTC brands and agencies who panic-kill creative the second CPA spikes. If you've watched ROAS fall off a cliff and opened Ads Manager with ten tabs going, you already know what happens next. Your gut says "creative fatigue." You kill your best-performing ad. A week later performance is still broken, because that was never the problem. Guessing wrong is the most expensive move in paid social. This workflow ends the guessing: → One agent investigates each competing theory — creative fatigue, budget and delivery changes, traffic quality, offer and seasonality → Each one is blind to the others, reasoning only from its own slice of the data so they can't bias each other → A refuter agent then attacks every surviving theory and tries to kill it → A theory only stands if the data can't disprove it → You get a ranked diagnosis: the real cause, the evidence for and against it, and the one move to make this week No anchoring on the first obvious answer. No killing winning creative on a hunch. No "here's what happened" reports that never tell you why. What you get: → Every theory tested in parallel instead of one biased guess → An adversarial pass that kills the wrong answer before you act on it → A ranked diagnosis with confidence levels and evidence both ways → A reusable workflow you drop next month's export into and re-run Built 100% in Claude Code with the new dynamic workflows. The first account I ran it on looked like textbook creative fatigue. The workflow disagreed, and traced the real cause to a budget change that had doubled spend and flooded delivery with junk traffic. I put together a full playbook with the exact workflow, the prompt, and how to run it on your own account. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

12,884 Aufrufe • vor 4 Monaten

Today I had my first demo drive in a Tesla. It was also my first time ever sitting in one. This was the first car I’ve ever sat in the driver’s seat of where I didn’t touch the steering wheel for over 20 miles. Before I even got to the car, the people who had demoed it before me were an older married couple who were absolutely euphoric. They thought it was so cool that the car could drive itself. The Tesla employee told me this happens all the time. People come back from demo drives and tell the next test driver that they’re about to have an amazing experience. Little did I know, I’d end up carrying on the torch to the next couple demoing it after me. There was a ton of construction where I demoed the car, and FSD handled the entire drive extremely well. And yes, it can go through a drive-thru and stop at each window. The only thing I had to do was tap the pedal because it wouldn’t leave on its own, but it was still wild seeing the AI stop perfectly at the second window and wait. There are a million things I could write about why a Tesla feels like a better car and how much more it offers compared to a regular car. But for now, I’ll stick to FSD. There were only two moments that made me a little uneasy. The first was pretty minor. The car slightly hesitated going up a driveway, but quickly made up its mind. The second was more noticeable. I didn’t realize the car was nagging me. Once I touched the steering wheel, nothing happened, so I pulled it right a little harder, then let go. After that, the car turned left and crossed a double yellow on a backroad. (and yes I know you can sue the volume knob) I’m not totally sure if it was trying to pull over or what it was doing. I wanted to see how it would handle the situation, but there were cars coming, so I took over and corrected it. One of the coolest moments was when I thought FSD was glitching because it came to a complete stop in the middle of a busy road. Then I looked around and realized why. On the right side, there was a bicyclist waiting at a yellow crosswalk. The cars behind me didn’t honk, and the Tesla stopping actually incentivized another car in the right lane to stop and let him pass. The car is almost too nice to pedestrians, because 99.999% of humans would’ve blown through that, especially with no flashing light. For 99.9% of the drive, the car navigated confidently and smoothly. It was a real “feel the AGI” moment. Please do not let the media, the general public, or anyone else convince you that this technology is just some kind of auto assist or glorified cruise control. This is undoubtedly getting extremely close to feeling superhuman. You still have to pay attention to the road, but after experiencing it myself, I’d be shocked if HW4 Teslas aren’t unsupervised within the next couple years. The car was extremely smooth. There was no harsh braking, and it even avoided something in the road that I didn’t see. Driving with FSD made me realize I probably wasn’t driving as well as I could be. Hopefully, eventually, everyone’s car can be as mindful as a Tesla. I’ve never seen a brand so far removed from the public’s sentiment. I’m so happy I ordered one.

Chris

18,859 Aufrufe • vor 3 Monaten

this is more useful than my entire degree Elon Musk's rocket company signed a $60,000,000,000 deal for Cursor in June, and eight days ago the two of them put a worker on sale for $200 a month: it gets its own computer in the cloud, signs into your accounts, clicks through your real apps, and hands back finished work instead of a draft for you to paste i ran one against my receipts folder on sunday and got back 14 filed, 2 it held because they needed a card number, and a saved method i never wrote myself Grok Bot is the one you train by doing your own job in front of it, and the whole handover fits in four messages tonight: 1. write out one job you did today the way you would brief a new hire: what has to be finished, which sites and files to work from, what to hand back, and where it stops and asks you 2. let it run once on something safe to get wrong, then correct the result until it is worth your name 3. say "save what we just did as a skill", and add the one rule about what always needs your approval 4. say "run that skill every weekday at 8 and post the result here. if the source is missing, tell me instead of using yesterday's numbers" xAI wrote that order into its own manual: one real job, then the saved method, then the clock. a schedule sitting on top of a method nobody checked replaces two hours of your clicking with two hours of your mistake turns out you never get to pick the brain, and that is the part i would argue about: the manual says there is no model picker for members or admins, no plan to add one, and the bill follows whichever model answered bookmark this, then open the piece below: which jobs deserve a worker of their own, and which ones quietly burn the seat ↓

Argona

21,946 Aufrufe • vor 1 Monat

Hold up, here is the prompt: works with almost any model. enjoy :) Role & Objective: Act as an Elite UI/UX Front-End Engineer specializing in Apple-tier micro-interactions and advanced CSS. Your task is to program a perfectly centered navigation bar in a strictly SINGLE HTML file containing all HTML, vanilla CSS, and vanilla JavaScript. No external libraries or frameworks (No Tailwind, React, etc.). Design Concept - "True Liquid Glass": CRITICAL INSTRUCTION: Do NOT generate standard, flat "glassmorphism" or basic frosted glass. I require a physically accurate "Liquid Glass" aesthetic. It must look like wet, poured clear resin, combining the high-gloss specular highlights of classic macOS Aqua with the volumetric spatial depth of modern Apple VisionOS. 1. The Liquid Glass Material & Lighting (CSS): - Deep Refraction: Use `backdrop-filter` with extreme blur (e.g., 50px) and over-saturation (200%). - Specular Highlight: Create a curved, semi-transparent white gradient on the top half using a pseudo-element (`::before`) to simulate a hard light reflection on a wet, rounded 3D surface. - Caustics & Volume: Use multi-layered inner and outer `box-shadow` properties to simulate light refracting at the bottom edge and casting a realistic ambient drop shadow. - Interactive Glare: Implement a soft radial-gradient spotlight inside the glass that dynamically tracks the user's mouse cursor (X/Y coordinates) using JavaScript and CSS variables (`mix-blend-mode: overlay`). 2. Navigation Layout & Elements: - Center the pill-shaped navigation bar perfectly in the middle of the viewport. - Include 3 main navigation items with minimalist, inline SVG stroke icons and text labels: "Home", "Call", and "List". - Add a subtle vertical divider line after the main buttons. - Next to the divider, add a Dark/Light Mode toggle button containing inline SVG Sun and Moon icons. 3. Animations & "Apple Magic": - Sliding Active Pill: Create a solid background "pill" that sits *behind* the active navigation item's text/icon. When a different item is clicked, this pill must dynamically recalculate its width and slide to the new position. - Spring Physics: The sliding transition MUST use an exact Apple-style bouncy spring easing curve (e.g., `transition: all 0.5s cubic-bezier(0.34, 1.2, 0.64, 1)`). - Tactile Feedback: Buttons and icons must physically press down slightly (`transform: scale(0.92)`) when clicked (`:active`). - Theme Switch: The Sun and Moon icons must smoothly rotate, scale, and cross-fade during the transition. 4. Background Environment (Crucial): - Glass needs light and color to refract! Create a full-viewport, smoothly animated mesh gradient background using 3 large, heavily blurred, floating color blobs. - Implement full Dark/Light mode logic using CSS variables (`:root` and `[data-theme="dark"]`). Toggling the theme must seamlessly transition the background blob colors, glass opacity, shadow intensity, and text colors. Output ONLY the pristine, production-ready code. Prioritize maximum visual fidelity and silky-smooth 60fps animations.

Leon Lin

128,501 Aufrufe • vor 6 Monaten

Everyone explains “As above, so below” incorrectly and that is why they miss its true power. They reduce it to a pleasant formula of manifestation: think positively, visualize what you desire, and the Universe will reproduce it. But this is merely the surface. The true principle is far more profound and far more demanding. “Above” is not the sky, and “below” is not the earth. Above is the archetype: the invisible order, the cause before the event, the intelligence before the form. Below is that same intelligence condensed into the body, matter, relationships, circumstances and time. “As within, so without” does not mean that every passing thought immediately creates your life. It means that whatever remains enthroned within you will eventually seek a body outside of you. A hidden fear becomes a pattern. An unhealed wound becomes a choice. A divided will creates a divided path. An embodied truth becomes presence, magnetism and direction. Through years of ritual work, energetic reading and confronting my own inner worlds, I have learned one undeniable truth: the visible almost never begins in the visible. You may change the person, the city, the altar, the business or the method—but if the unseen architecture remains untouched, the same lesson will return wearing another face. The world is a mirror, but not a shallow mirror. It does not merely reflect what you desire. It reveals what you serve, what you tolerate, what you secretly fear, what you have made sacred and what you are finally ready to transform. The natural world is the Mental made visible. The seed carries its invisible design before becoming a tree. In the same way, every material form is preceded by a subtler order. Ritual is the conscious bridge between these two worlds. The essence was never: control reality with your thoughts. The essence is this: become so internally ordered that your outer life can no longer remain loyal to your former chaos. Stop fighting the reflection. Enter the unseen cause. As above, so below. As within, so without. The seen is the mirror of the unseen. ✨🙌🏾💫

🧬Maxpein🧬

22,207 Aufrufe • vor 1 Monat

AI has had exactly two scaling axes that worked so far, and the second one is starting to look finite too the first one was pretraining: with scaling parameters and data, we got world knowledge (i.e. ChatGPT had read enough to know things), but it started saturating a while ago the second one was RL, and people had been doing RL the whole time before that: RLHF is RL but it never scaled far because it was trying to control the exact output, which tokens come out, how the text reads, but you can only push that so far before you’re just polishing RLVR dropped that constraint: giving the model a task, then checking whether the final answer is right, and ignoring everything in between -- so the model does whatever it wants in the middle and only the endpoint gets graded, and that’s much closer to actual RL and it’s what bought us planning and reasoning (arguably, tool use sits around 2.5 on this list -- while useful, it's not a different kind of thing) so one axis gave knowledge, the other gave reasoning, and both of them are one model working alone the next axis is how many models you can get working on the same problem, which is a different kind of axis than the previous two we know that multi-agent RL has always been the harder problem: I spent years in that literature and the gap between single-agent and multi-agent is definitely not incremental -- it’s a whole different class of difficulty! which is also why the derivatives are steep at the start, nobody has picked the easy wins yet... and the thing that gates this multi-agent coordination is communication: models can only coordinate as well as they can exchange information, and right now they do that by writing sentences to each other imagine what could we possibly achieve if we properly open that third axis development by letting models to exchange information in their native "language" without loosing any computational data that they produce during inference

Sasha Malysheva

15,053 Aufrufe • vor 1 Monat

Most people think their AI is not smart enough. It is smart enough. It just knows nothing about you. Every chat starts from zero. You paste the doc. You explain the project. You explain the same project again tomorrow. I finally fixed that part: 👇 I have been running Littlebird for a while now. The idea is simple. It is a desktop app for Mac and Windows that reads the text on your active window and sits in on your calls. So it already knows what you have been working on before you ask it anything. You do not brief it. You just ask. What that looks like in a normal day: 1/ Chat that already has the context No pasting. I ask what changed in a brief last week and it answers from the actual document that was open on my screen. 2/ Meeting Notes that write themselves It transcribes the call, then hands me the decisions and the action items. I get to stay in the conversation instead of typing through it. 3/ Routines that run on a schedule A morning briefing. A weekly summary of what I actually shipped. It shows up on its own. 4/ Hummingbird for the small stuff It appears right where you are working, so a quick question does not cost you a window switch and ten minutes of drift. The point is not the notes. Plenty of apps take notes. The point is that I stopped re-explaining my own work to a machine fifteen times a day. Free plan if you want to test the idea before deciding. Link is in the first comment, along with a discount for new users.

Mushfiq Sajib

66,683 Aufrufe • vor 28 Tagen

If you’ve ever managed custom icons in React Native, you know the frustration of choosing between performance and developer experience. Libraries like 𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝘀𝘃𝗴 are flexible but heavy. Every icon creates its own React subtree. The alternative? Manual icon fonts that force you into a constant back-and-forth of using web tools like IcoMoon and syncing font assets every time a design changes. 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗠𝗮𝗻𝘀𝗶𝗼𝗻 𝗟𝗮𝗯𝘀 just released 𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝗻𝗮𝗻𝗼-𝗶𝗰𝗼𝗻𝘀 to solve exactly this. It’s a build-time icon font generator that gives you the performance of native fonts with the flexibility of simple SVG files. 𝗪𝗵𝗮𝘁’𝘀 𝗵𝗮𝗽𝗽𝗲𝗻𝗶𝗻𝗴? Instead of rendering complex vector paths at runtime, this library automatically converts your folder of SVGs into an optimized icon font during the build process. It essentially teaches your app to treat icons like standard text characters, which allows it to bypass React’s component tree and layout engine entirely. ➡️ 𝗕𝘂𝗶𝗹𝗱-𝘁𝗶𝗺𝗲 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻: It handles the entire pipeline—watching your icon folder, converting SVGs to .ttf files, and linking them to your native project automatically. ➡️ 𝗡𝗮𝘁𝗶𝘃𝗲 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲: Because icons render as native text glyphs, it is significantly faster than traditional SVG rendering, making it the ideal choice for long, scrollable lists or icon-heavy dashboards. ➡️ 𝗘𝘅𝗽𝗼 𝗖𝗼𝗻𝗳𝗶𝗴 𝗣𝗹𝘂𝗴𝗶𝗻: It features first-class support for Expo, automating the native plumbing like Info.plist updates and asset linking during the prebuild phase. ➡️ 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗰 𝗧𝘆𝗽𝗲 𝗦𝗮𝗳𝗲𝘁𝘆: The library generates TypeScript definitions for your icon set, providing full IDE autocomplete and ensuring you never break the UI with a misspelled icon name. 𝗪𝗵𝘆 𝗶𝘁 𝗺𝗮𝘁𝘁𝗲𝗿𝘀? In high-performance applications, small overheads add up. By shifting the heavy lifting from the mobile device to your build machine, 𝗿𝗲𝗮𝗰𝘁-𝗻𝗮𝘁𝗶𝘃𝗲-𝗻𝗮𝗻𝗼-𝗶𝗰𝗼𝗻𝘀 ensures your UI stays buttery smooth while keeping your developer workflow modern. It’s another great example of how 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗠𝗮𝗻𝘀𝗶𝗼𝗻 continues to solve the "last mile" of performance friction in the ecosystem. Before you migrate your entire library, keep in mind: this is designed for the 𝗡𝗲𝘄 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 (Fabric) and requires React Native 0.74 or higher. #ReactNative #Expo #SoftwareMansion #Icons #MobileDev #Performance #DeveloperExperience #OpenSource #JavaScript #TypeScript #SVG #Fabric

The React Native Rewind

24,992 Aufrufe • vor 5 Monaten

𝕿𝖍𝖊 𝕮𝖍𝖆𝖎𝖓𝖘 𝖂𝖊𝖗𝖊 𝕹𝖊𝖛𝖊𝖗 𝕾𝖙𝖗𝖔𝖓𝖌𝖊𝖗 𝕿𝖍𝖆𝖓 𝕿𝖍𝖊 𝖂𝖎𝖑𝖑 𝕿𝖔 𝕰𝖘𝖈𝖆𝖕𝖊 The light over the sink was the color of a held breath. She stood there long enough for the tap to stop dripping and the house to go quiet around her, as if even the walls had decided to watch. Steam ghosted the glass, then thinned, and two angels looked at each other through what was left. One of them was wounded. Her wings, if they had ever been wings, hung wrong. Not broken in the pretty way stories like to paint. Broken in the living way. A shoulder drawn in. A mouth that remembered how to smile and no longer trusted the reflex. There was a mark violence leaves that no one else can point to and still she felt it, a wound under the skin. She had survived the night and then survived every morning after it, which is a second violence nobody counts. Across the glass the other angel was whole. Same face. Same bones. A version of her that still believed a room was only a room. Her hair fell the way it used to, easy, unguarded. Her eyes had not yet learned to measure a doorway or a tone of voice that changes too fast. She looked back with a brightness so intact it felt like a door slammed on a hymn. The wounded one wanted to hate her for it. She wanted to fall into her. She wanted to warn her. She could do none of those things. The glass would not allow passage. Time would not either. They stared until the air between them felt heavy. This was not one woman and her reflection. This was a threshold. Before and after occupying the same small bathroom, breathing the same cheap soap, refusing to blink first. She lifted her hand. The whole one lifted the same hand, a heartbeat late, as if memory had to catch up with the echo. Fingertips found the cold. Two lives met and failed to touch. The glass held them apart with a cruelty so ordinary it almost passed for furniture. Speak, the wounded one thought, though she did not know which of them she meant. The whole angel had no language for what was coming. That was her holiness and her helplessness. She could only remain as proof. Proof that there had been a self before the theft. Proof that the woman on this side of the glass was not a different creature, only a life interrupted and forced to continue. Something in the wounded angel’s chest tore and then... impossibly... kept beating. She didn't smash the mirror. People who have already been shattered learn the cost of breaking more glass. She looked until the two faces burned into one another: the girl who walked into the world unarmored, and the woman who walked out of the dark carrying her name like a lit match in a wind. When she finally turned from the sink, the whole angel did not vanish. She came too, folded into the wounded one the way a former country lives inside an exile. Not as a ghost. As a claim. Nearly 1 in 3 women on earth will stand at some version of this glass. The World Health Organization names it without poetry: physical violence, sexual violence, or both, at least once in a lifetime. Hundreds of millions. In the United States the numbers do not grow kinder. About 1 in 4 women report completed or attempted rape. Older national counts still used by survivor networks say 1 in 6. Most never see a courtroom. Most already know the face. The world prefers the whole angel in the glass. The world is less eager to look at the one who had to keep living in silence. I am one of these angels and so are many others. 💫This post is dedicated to all the other angels who remember like it was yesterday.

Lj Priest (Trader Jill)

18,361 Aufrufe • vor 12 Tagen