George Bardi

[George Bardi @geobde]

Introducing Graphql Explorer!

Generate GraphQL query from simple text prompts

Open Source→ https://t.co/e1kQWTZpsP

The UI is generated by @v0

[George Bardi @geobde]

#Hash for state management
https://t.co/i1zqICSKLM

[v0 @v0]

Paid users can now import designs from Figma as a starting point for generations.

[John Carmack @ID_AA_Carmack]

Act on press

This is a UI design hill I will die on, and it dismays me how often and hard I have had to fight for it.

Almost all interaction methods have a “press” and “release” event associated with them. Whenever possible, you should “do the thing” when you get the press event instead of waiting for the release event, because it makes the interaction feel substantially more responsive, and it reduces user errors by not allowing the focus to slide out of the hot box between press and release.

Even a “ballistic tap”, where your finger is intentionally bouncing off the button or touch surface, involves several tens of milliseconds delay between the press and release, and most button presses have well over a hundred ms dwell time. There is a delight in interfaces that feel like they respond instantly to your wishes, and the benefit to every single user is often more important than additional niche features.

Game developers, with simple UI toolkits, tend to get this right more often, but “sophisticated” app designers will often fight hard against it because it is mostly incompatible with options like interactive touch scrolling views, long press menus, and drag and drop.

Being able to drag scroll a web page or view with interactive controls in it is here to stay, and nets out way better than having to use a separate scroll bar, but there are still tons of fixed position controls that should act on press, and it is good UI design to favor them when possible.

In the early days of mobile VR, the system keyboard was a dedicated little OpenGL app that responded instantly. With full internationalization it became prudent to turn it into a conventional Android app, but the default act-on-release button behavior made it feel noticeably crappier. The design team resisted a push to change it, and insisted on commissioning a user study, which is a corporate politics ploy to bury something. I was irritated at how they tried to use leading questions and tasks, but It still came back one of the clearest slam-dunks I have seen for user testing – objectively less typos, expressed preference, and interview comments about the act-on-press version feeling “crisper” and “more responsive”.

So, I won that one, but the remaining times I brought it up for other interfaces, I did not, and you still see act-on-release throughout the Meta VR system interfaces.

[Jarred Sumner @jarredsumner]

We're hosting a Zig meetup in San Francisco at our office on Jan 10 at 5:30pm

https://t.co/Ex1gXmXA8Z

[Vercel @vercel]

v0 is now open for everyone.

Generate UI in seconds with text or images.

https://t.co/nojFCpeGx1

[Addy Osmani @addyosmani]

Third-party scripts can heavily impact performance.

@googlechrome is happy to partner with @nextjs & frameworks on smarter ways to load them via new wrapper components 🙏

https://t.co/wzlbgsQ3v6

[George Bardi @geobde]

@rauchg @nextjs @v0 https://t.co/erHPdtcxqV is 100% with v0 and the result is great!

[George Bardi @geobde]

@0x41_0x4C @v0 @0x41_0x4C please take a look https://t.co/erHPdtcxqV

[George Bardi @geobde]

Introducing Graphql Explorer!

Generate GraphQL query from simple text prompts

Open Source→ https://t.co/e1kQWTZpsP

The UI is generated by @v0

[George Bardi @geobde]

@IrvinZhan @v0 @jaredpalmer based on @IrvinZhan comment
i think is a good idea for @v0 to have like a showcase section with products totally build with v0!

[George Bardi @geobde]

@devagrawal09 and now easy https://t.co/erHPdtcxqV 😂

[Jarred Sumner @jarredsumner]

Bugzilla (released in 1998) shows related & possibly duplicate issues when filing a new issue

I wish @github did this

[Vercel @vercel]

Next.js 13.5

◆ 22% faster local server startup
◆ 29% faster HMR (Fast Refresh)
◆ 40% less memory usage
◆ Optimized package imports
◆ `next/image` improvements
◆ And over 438 bugs patched!

https://t.co/edW10gB19X

[Jarred Sumner @jarredsumner]

Bun 1.0 is compiling

https://t.co/sxAKXDzrOd

[Lior Alexander @LiorOnAI]

Article: https://t.co/32r5Lm8vZ1

Github: https://t.co/oqnMvXQz6k

Congrats @jadecopet, @syhw, @jpineau1, @ylecun

[Nicole Sullivan @nicolesullivan.bsky.social @stubbornella]

Introducing the popover API in Chromium 114! Look ma, no javascript! https://t.co/0KxV4VqdP3

[George Bardi @geobde]

@darylginn Lato

[George Bardi @geobde]

https://t.co/n3w6uGqbkD

#React #webperf

[Guillermo Rauch @rauchg]

Agreed!

With @nextjs 13 app/, each "microfrontend" within a project can grow in complexity *locally* instead of polluting the global shared fs.

Our new filesystem router is bringing to apps the same local-reasoning benefits React brought to UI components 🤯

[React @reactjs]

The React Documentary premieres in about 3 hours. This is the origin story of React. Join us for a trip down the memory lane to when React was not the global community it is today, but only a fragile, strange, fascinating idea that almost didn’t happen. https://t.co/6CYmmNeFRd