CASE STUDY 05 / Developer tools · Internal platform

Internal Low-Code Platform

Built composite components and theme switching for a low-code platform that helped internal marketing and construction teams assemble simple apps. The platform began in Vue 3 and later moved to Vue 2 to join the company’s wider micro-frontend system.

Commercial work · Interactive reconstruction

CONTEXT

Longshine

MY ROLE

Frontend development · Composite components & theming

TOOLS & FOCUS

Vue 3 → Vue 2 · Composite components · Drag-and-drop · Theming

INTERACTIVE BUILDER

Build your own app.

Compose a page, arrange its fields and change the theme. Then try the app you made.

FIELD NOTESLIVE CANVAS

A better day in the field.

Site name *

Priority

Drop inside Site visit

+ Drop a component on the page

Drag a component, or click to add it.4/10 components

Interactive reconstruction · Sample components and local data.

01 / THE PROBLEM

What needed to work.

As low-code development gained momentum, we built an internal platform for the marketing and construction departments to assemble simple apps from reusable components. My technical challenges centered on composite-component data flow, drag-and-drop parent-child relationships and consistent theme switching.

CONCEPT / 05

01Reusable components

02Page hierarchy + data flow

03Marketing + construction apps

Illustrative workflow · Not a product screenshot

A summary of my responsibilities and technical approach. This workflow illustration does not reproduce the product UI.

02 / MY CONTRIBUTION

Where I took ownership.

Participated in technical selection and developed composite components for the internal low-code platform.
Worked on data-flow design between composite components and their nested fields.
Handled drag-and-drop hierarchy so component placement and parent-child relationships stayed consistent.
Implemented theme switching across the assembled application.

03 / TECHNICAL APPROACH

Decisions in context.

Design the data flow of a composite component

My work included composite components made from smaller interface elements. Designing how their data flowed between the component and its children was a central difficulty: the assembled page needed coherent values and configuration as it was edited.

04 / DELIVERY & REFLECTION

What I can share.

Delivery.

Commercial frontend work on composite components, component data flow, drag-and-drop hierarchy and theming. The interactive builder is a new portfolio reconstruction using sample components and local data; it does not reproduce proprietary source code or the original product UI.

Have a similar challenge?

Let’s talk ↗