Onlook viewer

The full “closed-loop” of the product so that the platform is usable from steps 1 to 3. AI entered the chatLast month, we shipped our translation layer built on top of state-of-the-art language models. To make it really easy to understand, we made it so that when designers make a design edit, AI finds what to change in the code, and makes the change. Fun!AI allows us to push code changes that work with the team’s codebase in their own setup, making Onlook the perfect plug-and-play solution for any team. We hope to continue building out our AI suite to allow designers to not only ship code but also ship better UI code than the average engineer. Here’s a change where the AI added a UI change but also fixed a subtle bug (can you spot the bug?).Daniel shipped 4 pull requests using OnlookWith our release of pushing to code, our designer numero uno (Daniel) has made significant UI changes to the codebase using only Onlook without needing to clone the repo or run it locally. To be specific, Kiet made a Feedback form, Daniel jumped in and styled it to look way better, and Kiet merged the code that Onlook produced into production all within a few minutes. This is a huge unlock for the velocity of the team shipping and also validates the value of the platform. Currently, we still have to review the changes manually before pushing, but as the platform matures, we hope to cut this

Capabilities such as inserting new components like buttons, text, frames, etc. which will be a huge benefit to getting designers full control over the designs. Intros to product designers at smaller teams and Series A startups that would be open to adopting this tool. We’re focusing on designers with influence, familiarity with code, or the ability to access GitHub. Intros to investors and angels in the dev tools / design / AI space who’d be interested in what we’re doing.We still feel very early in terms of what our product is and can be, and we’re grateful for your patience and support as we continue to discover what Onlook is in these first few months. The biggest milestone has been us using the tool internally to make changes to the product, so we’re definitely excited to keep testing it internally and improving it. If you’d like to try it out, let us know and we’d be happy to share a demo!Best,Kiet & Daniel Cofounders of Onlook with mega kudos and support from Erik NelsonDiscussion about this post

Review process down to zero. (See Daniel’s GitHub contributions below)Editor joined the dark side As a side effect of following users' feedback, the editor got major improvements both on UI and functionality. It’s starting to grow out of its awkward teenage phase and is now in its underclassmen-in-college phase, striving for full maturity, but still with a few quirks and some personal skills that need a bit of polish. We’re hoping intramural soccer will help. The editor now supports a layers view, undo-redo, multi-select, and even a mini code editor. Here’s an action shot.(nice!)In January our biggest challenge was the quality and usability of the editor. Now that we’ve solved that, our biggest challenge in February has been getting fans / users / advocates at companies to feel comfortable enough to add our product to their codebase. Despite the enthusiasm for the product, many designers drop off at the point where they need to configure their codebase. This is due to either lack of access to the codebase or to our onboarding process being too confusing.Our goal for March is to onboard 3 teams to start making pull requests through Onlook. In order to do that, we’re going through our waitlist and searching for advocates at organizations who would be open to being an early adopter of our product. To continue to make it easy for people to use Onlook, we’ll be adding an improved onboarding experience with demo projects as well as developer docs. We’re also adding more editing

The most common phrasal verbs native speakers usually use in their daily life.Each phrasal verb is well explained and demonstrated with phrasal verb meanings (definitions) together with phrasal verb examples. There are also high-quality audio recordings of the example which will definitely benefit your listening and speaking practice. Start the first lesson now, and start speaking like a native-like English speaker.Phrasal verbs list with “Come”Come up Come up withCome acrossCome aroundCome aboutCome alongCome outCome backCome overCome throughCome apartCome beforeCome uponPhrasal verbs list with “Take”Take offTake outTake placeTake overTake afterTake awayTake apartTake onTake upTake up onTake up withTake downTake againstTake asideTake throughPhrasal verbs list with “Get”Get upGet overGet on with (so) Get rid of (st,so) Get out of (doing st) Get through to (so) Get awayGet togetherGet back at SOGet acrossGet back withGack toGet behind (with something)Get downGet in onGet onGet offGet throughGet roundGet ontoPhrasal verbs list with “Look”Look atLook forLook upLook out/to watch out (for)Look over/to go over/to read over/to check overLook up toLook aheadLook down onLook forward toLook in onLook toLook throughLook upon asPhrasal verbs list with “Go”Go on/to keep onGo aboutGo alongGo awayGo forGo overGo acrossGo afterGo againstGo aheadGo along withGo back onGo beforeGo downGo underGo intoGo offGo off withGo throughGo through withOther common phrasal verbsTry onThink overSit downDress upTire outHang upCount on/to depend onPoint out Figure out Wake upHurry up Lie downTalk overBreak downGive upCross outCome across/to run acrossStay upRely on (upon)Show upFind outDrop out ofDrop by/inBelieve inCheer upFade awaySell outSave upCheck outShow offWork outCall offMess upNarrow

For our first post we wanted to share our monthly update we wrote for the end of February. It shows some of our thinking on the product and where we’re at with development. Enjoy!As a reminder, Onlook turns any product team into an engineering team by making it super easy for designers to edit designs directly in production, and then effortlessly push their changes to GitHub.Daniel flew out to pow-wow in CincyWe’re interviewing 3-4 teams weeklyAI is now integrated into the core productDaniel pushed 4 PRs into production using OnlookEditor experience is no longer a blocker for people to use the toolFirst team onsiteDaniel left his apartment in smalltown NYC to experience the splendor of Cincinnati for 1 week with Kiet and Erik. He got a nice Cincinnati welcome with dinners at OTR classics like Abigail Street, the Eagle, Teak, etc. We also used this chance to focus on company values, culture, fundraising, and planning out our releases for Q1. Here are two pics:Where Erik convinced us that Apple Vision Pros may be a respectable employee perk to offerFeast on how much work we did right before we erased it all on this whiteboardUser interviewsThe team has averaged 3-4 user interviews per week since last month. The feedback has been trending more positive as we’ve continued to improve the application, yet we still are looking for our early adopters to fully integrate our product into their workflow. We think of the product in three stages: EditingSharingSubmitting codeThis month we achieved

Video walkthroughArchitecture walkthrough video: Intro00:15 What is Onlook1:37 Directory structureElectron:2:09 Electron architecture3:11 Electron Node serverReact app:3:34 React Browser window5:44 React app6:14 Routing7:07 Editor pageWebview:9:12 Webview11:23 Webview scriptUpdating style:13:14 How update style works - Concept14:08 How update style works - Code16:08 Update style action18:42 How update style writes to codeAI Chat:24:43 AI Chat demo26:44 Conversations29:21 Prompting30:38 Resolving the stream responseConclusion32:41 Closing33:36 Contact me with any questionsPrevious walkthrough videoAug 28th, 2024Jul 10, 2024High-level architectureTypical electron architecture with an extra web view that holds the users' pageTechnical detailsHight-level overviewVisual editingOnlook is technically a browser that points to your localhost running the app. It can manipulate the DOM like a Chrome Devtool, and all these changes are injected into the page through a CSS stylesheet or DOM manipulation. The changes are non-persistent until written to code.Write to codeTo translate the changes to code, we inject an attribute into the DOM elements at build-time that points back to the code like a sourcemap. The attribute gives us the location of the code block, and the component scope [1]. We then find the code, parse it into an AST, inject the styles, then write it back.Framework supportThis technique is framework agnostic as we can swap in a different compiler for another framework[2]. It can work for any codebase as we’re just using open standards that don’t require any custom code. The code generated is written directly into your codebase, locally, so you can always take the output without being locked-in to the tool.ActionsAll the changes made are stored as actions. This allows them to be serialized, stored, and reproduced. We did it this way so eventually, we can introduce online collaboration or let an agent generate actions. To do this, we’d just need to serve the locally running page and resolve incoming actions.How the canvas worksHow auth worksWe use Supabase for auth. When a Supabase token is found in .env or bundled into the env variables, we enable Supabase capabilities such as auth.When authentication starts, we open the OAuth page using the user's default browser. This redirects back to the electron app as the URL: onlook://auth#params wherein the params gives token access. We securely store these tokens and use them to access Supabase resources.How edits workHow edits happen between the DOM, and writing to codeWalkthrough video: Intro00:15 Editing element00:56 How the edits work02:10 Other details