The first release as standalone desktop and mac version of Lapin can be found on the https://ciuntucbimstudio.ro/en/#projects website.

Meet Bubbles - your friendly house designer assistant This is only a UI layer built on top of the BubbleBIM engine - can help you ideate fast your dream home ideas. No tech skills needed. Having in it's core DNA the architectural norms, and also structural guidlines, it can be a good interface between the non-techical customer and the architectural savy experts and engineers. The final model is a bbim model - fully parametrical, editable, and can be sent to ArchiCAD via Tapir (and probably Revit - if I invest time into it in the future) for further design development. P.S. This is just a proof of concept stage, but could be a thing. I leave the link for live testing here. What do you think? https://bbim.ciuntucbimstudio.ro/ https://youtu.be/7kW1Wib7Sik

No. The answer is no. While building Lapin, a BIM editor on top of the open-source ifc-lite engine, I kept running into the same thing. When you edit an .ifc model in place, every change has to become .ifc again. The elements you touched are written out as STEP text, parsed back, and their geometry rebuilt. The file stores the result: solids and placements, not the intent behind them. So I'm moving authoring to a native schema: • It stores intent, not results. A wall is its axis, height, type and storey, not a solid. Geometry is derived and can always be rebuilt. • It's IFC-shaped. It uses the same classes, PredefinedTypes and property sets, so export is a 1:1 translation, not a reinterpretation. • No STEP round-trip. Parameters go straight to the Rust geometry kernel as binary data. • Built for editing. Working tables are Apache Arrow, read directly into memory; Parquet stays for analytics. Early numbers: • Rebuilding geometry after an edit is about 11× faster for ordinary elements (~0.1 ms vs ~1.2 ms). Walls with complex boolean cuts are still on par. • Dragging a wall now shows the real geometry live, with material layers, joins and openings, at ~17 ms per move. Before, you saw a placeholder box. IFC stays where it shines. Imported models keep their IFC workflow, and every native element exports back to IFC without loss. Correct me if I am wrong, but the same problems as ifc I see in his binary, way more faster to parse in.a viewer brother .frag.

.ifc fileformat is aparently not built for a native editor. It works fine for small models. Once the model goes too complex, it get's to be slow. For an editor - this is a big problem. You must somethimes edit in bulk elements, load big models in the memory, reload parts of it at every change - it is an UX killer. So I am creating a new skema - a zip that acts like a datalake - and store there the information in the optimal way for it to be read, changed and rendered by the viewer. Also - Lapin will be local distribution, with an update from the cloud at new releases. At least, this is the plan.

I've created a live link where you can test the new clasical BIM modeler I've distiled from BubbleBIM on top of Ifc-Lite. https://lapinbim.vercel.app/ Still early development, and any sugestions and bugg reports are wellcomed. Lapin Lapin is a BIM application for modelling and documentation in the browser, built on the open-source IFClite toolkit. It opens, models, draws and documents IFC files entirely on the user's computer: there is nothing to install, and the models are never sent to a server for processing. Models and viewing - Opens IFC2X3, IFC4 and IFC4X3 files, as well as IFC5 (IFCX). Several models can be combined in one project. - Each model is either: - native: editable and saved inside the project; - linked: a reference used for coordination, which is never modified. - Loads files from disk or from connected cloud storage and common data environments. - A fast WebGPU 3D viewer: - orbit, walk and section planes; - measuring; - isolate, hide and filter by class, type, storey or material; - search, spatial tree and properties; - georeferencing. - Analysis tools: - IDS validation, BCF issues and clash detection; - model comparison; - entity lists and quantities, and charts bound to the model; - 5D cost and a construction schedule (Gantt); - scripts and node-based flows. - Project, views and sheets - Project navigator: levels, floor plans, sections, elevations, 3D views, schedules, road drawings, sheets and models. Each can be created, renamed, duplicated or deleted. - Every 2D view has: - a work plane; - a cut plane (1.2 m by default on plans); - a view depth. - Visibility / Graphics per view: - which categories show; - their line colour and weight; - their cut fill and cut hatch. - Building materials table: - each IFC material gets its cut hatch, fill and pen; - layered walls and slabs are hatched layer by layer; - the bands of the same material on neighbouring walls merge; - layers thinner than 2 mm (vapour barriers, membranes) are drawn as a heavy dashed line.