[{"data":1,"prerenderedAt":92},["ShallowReactive",2],{"service-en-aplikacje-webowe":3},{"id":4,"title":5,"body":6,"description":81,"draft":82,"extension":83,"kicker":84,"meta":85,"navigation":86,"order":75,"path":87,"seo":88,"stem":89,"summary":90,"__hash__":91},"services_en\u002Fservices\u002Faplikacje-webowe.md","Web applications",{"type":7,"value":8,"toc":73},"minimark",[9,14,18,21,24,28,31,34,38,41,45],[10,11,13],"h2",{"id":12},"scope","Scope",[15,16,17],"p",{},"We build web applications where the user has a job to finish, not a page to read. Dashboards, SaaS, configurators and internal tools: architecture, flow UX, front-end, API integration and code quality.",[15,19,20],{},"The stack is JavaScript and TypeScript — most often Vue.js and Nuxt, sometimes Node.js on the server. SPA when the application lives in the browser. We start from roles and paths, not from a colour palette. The app should be fast, accessible and possible to grow after go-live.",[15,22,23],{},"This is not “a theme rebuilt in Vue”. It is component architecture, state, routing, accessibility and performance — so the product can grow a year after launch instead of being rewritten at the first new feature.",[10,25,27],{"id":26},"vuejs-nuxt-and-typescript","Vue.js, Nuxt and TypeScript",[15,29,30],{},"Vue.js and Nuxt give control over UX and team speed: one language from interaction prototype to code. TypeScript lowers the cost of change in a web application. We pick this stack when WordPress cannot carry the logic, or when you need a complex front-end with roles and state.",[15,32,33],{},"We can also pair headless WordPress with a Vue.js front-end when content should live in a CMS and key views need an application.",[10,35,37],{"id":36},"who-its-for","Who it’s for",[15,39,40],{},"Teams that have outgrown a website or a spreadsheet and need a tool with login, permissions and state. If the process lives in inboxes and clients are waiting for “the system” — that is the product.",[10,42,44],{"id":43},"what-you-get","What you get",[46,47,48,52,55,58,61,64,67,70],"ul",{},[49,50,51],"li",{},"a map of roles, states and key flows",[49,53,54],{},"a UX prototype that can be built, not only presented",[49,56,57],{},"a front-end architecture (Vue.js \u002F Nuxt) fitted to the product",[49,59,60],{},"components and a design system you can ship screen by screen",[49,62,63],{},"API wiring, validation, error and empty states",[49,65,66],{},"tests where they protect flows, not where they pad a metric",[49,68,69],{},"code and notes a team can work with after handoff",[49,71,72],{},"a plan for care after launch",{"title":74,"searchDepth":75,"depth":75,"links":76},"",2,[77,78,79,80],{"id":12,"depth":75,"text":13},{"id":26,"depth":75,"text":27},{"id":36,"depth":75,"text":37},{"id":43,"depth":75,"text":44},"Web applications in JavaScript and TypeScript: dashboards, SaaS and internal tools. Vue.js, Nuxt, SPA, roles, state and APIs — from flow UX to launch.",false,"md","Apps",{},true,"\u002Fservices\u002Faplikacje-webowe",{"title":5,"description":81},"services\u002Faplikacje-webowe","Web products with logic, state and roles — dashboards, SaaS and internal tools.","-FdE50z984dD0J3FWuyk0_rMgg5tbeaNCac8I31RL_M",1789584540925]