{"id":2137,"date":"2026-08-19T19:01:15","date_gmt":"2026-08-19T12:01:15","guid":{"rendered":"https:\/\/webportfolio.macroglobal.tech\/cases\/dev-platform-a-corporate-tool-for-development\/"},"modified":"2026-08-19T19:01:15","modified_gmt":"2026-08-19T12:01:15","slug":"dev-platform","status":"publish","type":"isotope","link":"https:\/\/proptechservice.kz\/en\/cases\/dev-platform\/","title":{"rendered":"Dev Platform \u2014 a corporate tool for development"},"content":{"rendered":"
\n\t\n\n
\n\t\t\t\n\n

About the project:<\/h2>\n\n\t<\/div>\n\n\n\n
\n\t\t\t
\n\t\t\t\n\n

Dev Platform is a corporate tool for the development team. Built entirely by our team.<\/p>\n\n\n\n

What the product is for: to gather in one place what is usually scattered across different services \u2014 working environments, tasks and project files. A programmer opens one window and works, and a manager can see what is going on.<\/p>\n\n\n\n

This is not an experiment or a demo: the platform has been in production since June 2026 and serves a live team. Alongside it stands a corporate CRM for the sales team \u2014 two internal tools built in the same vein: one covers development, the other sales.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n

\n\t\n\n
\n\t\t\t\n\n
\"Dev
Personal and team environments: statuses, entry points, latest activity.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n\n\n
\n\n\n
\n\t\n\n
\n\t\t\t\n\n

The core idea:<\/h2>\n\n\t<\/div>\n\n\n\n
\n\t\t\t
\n\t\t\t\n\n

It started as programmer environments in the browser. The value turned out to lie elsewhere.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n

\n\t\n\n
\n\t\t\t
\n\t\t\t\n\n

Work runs in several streams at once, not in a single one.<\/strong> Generation is not a command you wait on, but a process that lives for tens of minutes. One stream means a person sitting idle. Here each stream runs in its own isolated environment: you can launch a dozen of them, spread them across different tasks, then step into any one and see what is happening there right now \u2014 not a report after the fact, but live work you can put your hands into and let go of again.<\/p>\n\n\n\n

A human stays in the loop, and verification is a mandatory step.<\/strong> The main trouble with generation is not syntax errors but a plausible result with a made-up justification. That is why verification in the platform is not the performer’s goodwill but a separate mandatory stage of the pipeline: «done» does not arrive until the result has been confirmed independently.<\/p>\n\n\n\n

The platform knows what the project is made of.<\/strong> It keeps a map of the project’s dependencies and relies on it so that second versions of what has already been written do not appear in the code. Plus a programmer’s familiar tools stay within reach \u2014 at any moment you can open a file and fix it by hand.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n\n

\n\n\n
\n\t\n\n
\n\t\t\t\n\n

Working sessions:<\/h2>\n\n\t<\/div>\n\n\n\n
\n\t\t\t
\n\t\t\t\n\n

The team works in isolated environments \u2014 one environment per project or workstream. The platform shows every session at once: which environment, which project, who owns it, when the latest activity was. A session opens straight from the interface.<\/p>\n\n\n\n

A session lives on the server, not in a browser tab. Close the laptop, open the phone: the same work, the same history, nothing lost. Inside the environment is everything a programmer is used to: a terminal, files, an editor with highlighting, a history of changes.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n\n

\n\n\n
\n\t\n\n
\n\t\t\t\n\n

Work from any device:<\/h2>\n\n\t<\/div>\n\n\n\n
\n\t\t\t
\n\t\t\t\n\n

Not «responsive design for the sake of it». Since the session lives on the server, the phone is not a stripped-down version but a second full-fledged entry into the same work.<\/p>\n\n\n\n

Almost everything comes down to one non-obvious thing: an on-screen keyboard has no Esc<\/code>, no Ctrl<\/code>, no Tab<\/code> and no arrows \u2014 and without them a terminal is useless, you cannot get out of the editor and cannot interrupt a process. So the mobile layout has a separate panel of these keys, and its modifiers are sticky, so a combination can be typed one-handed.<\/p>\n\n\n\n

The other sections are not dropped on the phone but rearranged: the sidebar becomes a slide-out drawer, the board’s columns scroll horizontally, a card opens full screen.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n

\n\t\n\n
\n\t\t\t\n\n
\"Dev
The keys missing from the on-screen keyboard get a separate panel with sticky modifiers.<\/figcaption><\/figure>\n\n\t<\/div>\n\n\n\n
\n\t\t\t\n\n
\"Full-screen
A full terminal on the phone \u2014 the same session that was on the laptop.<\/figcaption><\/figure>\n\n\t<\/div>\n\n\n\n
\n\t\t\t\n\n
\"Dev
The board: columns scroll horizontally, a card opens full screen.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n\n\n
\n\n\n
\n\t\n\n
\n\t\t\t\n\n

Tasks:<\/h2>\n\n\t<\/div>\n\n\n\n
\n\t\t\t
\n\t\t\t\n\n

Tasks are run on boards \u2014 one per workstream. Besides the boards there is a «today» view and task analytics.<\/p>\n\n\n\n

A task card holds more than a description: inside are checklists, priority, assignee, time tracking<\/strong> and a discussion \u2014 the correspondence on a task lives in the card itself, not in a separate messenger. You can see how much time went into a task and who on the team is online right now.<\/p>\n\n\n\n

And the same board is a queue for an agent. A card from a column can be handed not only to a person: an agent takes it on and, when finished, attaches proof of the result to the card and moves it along. A task counts as done only after independent verification.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n

\n\t\n\n
\n\t\t\t\n\n
\"Dev
The card: description, checklists, attachments, discussion \u2014 and a job for an agent.<\/figcaption><\/figure>\n\n\t<\/div>\n\n<\/div>\n\n\n\n
\n\n\n
\n\t\n\n
\n\t\t\t\n\n

Interface:<\/h2>\n\n\t<\/div>\n\n\n\n
\n\t\t\t
\n\t\t\t\n\n

Light and dark theme, two languages. The styling is terminal-like: monospace headings, a «console» layout, a calm background. Beneath the interface lies a design system of its own, against which all development is checked. Who on the team is online right now and who is looking at the same board is visible in real time.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n\n\n\n

\n\n\n
\n\t\n\n
\n\t\t\t\n\n

Result:<\/h2>\n\n\t<\/div>\n\n\n\n
\n\t\t\t
\n\t\t\t\n\n

The platform has been in production since June 2026 and serves a live team. A programmer opens a link and works \u2014 with no «install twenty things locally»; sessions survive a closed tab and a move to the phone; several parallel streams of work do not get in each other’s way, because each has its own environment.<\/p>\n\n\n\n

The product is large and alive: around 200,000 lines of our own code and almost two thousand automated checks that run on every change.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n\n<\/div>\n","protected":false},"excerpt":{"rendered":"

a corporate tool for development<\/p>\n","protected":false},"featured_media":1668,"template":"","class_list":["post-2137","isotope","type-isotope","status-publish","has-post-thumbnail","hentry","isotope_category-software-for-property-developers"],"acf":[],"_links":{"self":[{"href":"https:\/\/proptechservice.kz\/?rest_route=\/wp\/v2\/isotope\/2137","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/proptechservice.kz\/?rest_route=\/wp\/v2\/isotope"}],"about":[{"href":"https:\/\/proptechservice.kz\/?rest_route=\/wp\/v2\/types\/isotope"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/proptechservice.kz\/?rest_route=\/wp\/v2\/media\/1668"}],"wp:attachment":[{"href":"https:\/\/proptechservice.kz\/?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2137"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}