[{"data":1,"prerenderedAt":505},["ShallowReactive",2],{"docs-navigation":3,"docs-\u002Fstart\u002Fwhat-to-expect":264,"surround-\u002Fstart\u002Fwhat-to-expect":502},[4,33,96,124,183,222,241],{"title":5,"path":6,"stem":7,"children":8},"Start","\u002Fstart","1.start",[9,13,18,23,28],{"title":10,"path":6,"stem":11,"description":12},"Start here","1.start\u002Findex","What Desifex is, and how to get an application of your own running.",{"title":14,"path":15,"stem":16,"description":17},"What Desifex is","\u002Fstart\u002Fwhat-desifex-is","1.start\u002F1.what-desifex-is","An application factory where conversation is the interface — and the handful of things it deliberately will not do.",{"title":19,"path":20,"stem":21,"description":22},"Your first application","\u002Fstart\u002Fyour-first-application","1.start\u002F2.your-first-application","From a sentence to something running, in about twenty minutes, with nothing to install.",{"title":24,"path":25,"stem":26,"description":27},"The workbench","\u002Fstart\u002Fthe-workbench","1.start\u002F3.the-workbench","A tour of the screen you will spend your time on — the conversation, the seven tabs, and the menu.",{"title":29,"path":30,"stem":31,"description":32},"What to expect","\u002Fstart\u002Fwhat-to-expect","1.start\u002F4.what-to-expect","How long things take, what a good working rhythm looks like, and the parts that genuinely go wrong.",{"title":34,"path":35,"stem":36,"children":37},"Building","\u002Fbuilding","2.building",[38,41,46,51,56,61,66,71,76,81,86,91],{"title":34,"path":35,"stem":39,"description":40},"2.building\u002Findex","Getting what you actually wanted out of the conversation.",{"title":42,"path":43,"stem":44,"description":45},"Describing what you need","\u002Fbuilding\u002Fdescribing-what-you-need","2.building\u002F01.describing-what-you-need","How to phrase a request so that what comes back is what you meant.",{"title":47,"path":48,"stem":49,"description":50},"Watching a build","\u002Fbuilding\u002Fwatching-a-build","2.building\u002F02.watching-a-build","What the steps mean, what is happening underneath, and why you are not shown a log.",{"title":52,"path":53,"stem":54,"description":55},"Changing your mind","\u002Fbuilding\u002Fchanging-your-mind","2.building\u002F03.changing-your-mind","Interrupting a build, correcting a misunderstanding, and undoing something you asked for.",{"title":57,"path":58,"stem":59,"description":60},"More than one conversation","\u002Fbuilding\u002Fmore-than-one-conversation","2.building\u002F04.more-than-one-conversation","Putting a piece of work down and starting the next one cleanly — what the builder keeps, what it forgets, and when a fresh conversation is the right move.",{"title":62,"path":63,"stem":64,"description":65},"A board of work","\u002Fbuilding\u002Fa-board-of-work","2.building\u002F05.a-board-of-work","The Work tab — writing down everything you have thought of, deciding what is ready, and letting the builder take them one at a time.",{"title":67,"path":68,"stem":69,"description":70},"When a build fails","\u002Fbuilding\u002Fwhen-a-build-fails","2.building\u002F06.when-a-build-fails","What a failure actually means, what to try, and when to ask us.",{"title":72,"path":73,"stem":74,"description":75},"Showing it a file","\u002Fbuilding\u002Fshowing-it-files","2.building\u002F07.showing-it-files","Attaching a screenshot, a spreadsheet or a document to the conversation — often faster than describing it.",{"title":77,"path":78,"stem":79,"description":80},"Choosing a design system","\u002Fbuilding\u002Fchoosing-a-design-system","2.building\u002F08.choosing-a-design-system","What a design system decides, how to pick one, and what changing it later does.",{"title":82,"path":83,"stem":84,"description":85},"Asking for settings","\u002Fbuilding\u002Fasking-for-settings","2.building\u002F09.asking-for-settings","The conversation reaches the whole platform — addresses, icons, redirects, users, integrations and shipping. If you do not know where a setting is, ask.",{"title":87,"path":88,"stem":89,"description":90},"When it asks you","\u002Fbuilding\u002Fwhen-it-asks-you","2.building\u002F10.when-it-asks-you","Some decisions arrive as a screen rather than a message — a table to correct, a list to choose from — and the build waits for your answer.",{"title":92,"path":93,"stem":94,"description":95},"Starting from what you have","\u002Fbuilding\u002Fstarting-from-what-you-have","2.building\u002F11.starting-from-what-you-have","A spreadsheet, a document, a picture or a page of your own site — attached, read, and built from.",{"title":97,"path":98,"stem":99,"children":100},"Shipping","\u002Fshipping","3.shipping",[101,104,109,114,119],{"title":97,"path":98,"stem":102,"description":103},"3.shipping\u002Findex","Getting what you built in front of people, and getting back to an earlier version.",{"title":105,"path":106,"stem":107,"description":108},"Versions","\u002Fshipping\u002Fversions","3.shipping\u002F1.versions","Every build is kept, named after what was asked for, and can be compared and restored.",{"title":110,"path":111,"stem":112,"description":113},"Environments","\u002Fshipping\u002Fenvironments","3.shipping\u002F2.environments","Preview, test and live — what each one is, who can reach it, and why their data is separate.",{"title":115,"path":116,"stem":117,"description":118},"Deploying","\u002Fshipping\u002Fdeploying","3.shipping\u002F3.deploying","Putting a version into test or live, what happens while it deploys, and what happens if it fails.",{"title":120,"path":121,"stem":122,"description":123},"Going back","\u002Fshipping\u002Fgoing-back","3.shipping\u002F4.going-back","Restoring an earlier version when a change turned out to be wrong.",{"title":125,"path":126,"stem":127,"children":128},"Running","\u002Frunning","4.running",[129,133,138,143,148,153,158,163,168,173,178],{"title":130,"path":126,"stem":131,"description":132},"Running it","4.running\u002Findex","Everything in Settings — addresses, access, people, files, integrations and what crawlers are told.",{"title":134,"path":135,"stem":136,"description":137},"Addresses and domains","\u002Frunning\u002Faddresses-and-domains","4.running\u002F01.addresses-and-domains","The address an application gets, and how to put it on a domain you own.",{"title":139,"path":140,"stem":141,"description":142},"Who can reach it","\u002Frunning\u002Fwho-can-reach-it","4.running\u002F02.who-can-reach-it","Open, behind one shared password, or accounts — and why the choice is enforced in front of the application.",{"title":144,"path":145,"stem":146,"description":147},"People who sign in","\u002Frunning\u002Fpeople-who-sign-in","4.running\u002F03.people-who-sign-in","The workspace's user directory — adding the people who use your applications, which ones each may open, what you can keep about them, and two-step sign-in.",{"title":149,"path":150,"stem":151,"description":152},"Published files","\u002Frunning\u002Fpublished-files","4.running\u002F04.published-files","Documents your application hands to its users — a price list, a brochure, a form — with a stable address and no build to change them.",{"title":154,"path":155,"stem":156,"description":157},"Integrations","\u002Frunning\u002Fintegrations","4.running\u002F05.integrations","Email, SMS and Google — connected once, used by the application without it ever holding a credential.",{"title":159,"path":160,"stem":161,"description":162},"Appearance","\u002Frunning\u002Fappearance","4.running\u002F06.appearance","The browser tab, the icon, what a link looks like when somebody pastes it, and adding it to a phone's home screen.",{"title":164,"path":165,"stem":166,"description":167},"Redirects and search engines","\u002Frunning\u002Fredirects-and-search-engines","4.running\u002F07.redirects-and-search-engines","Old addresses that still get visited, and what crawlers are told about each environment.",{"title":169,"path":170,"stem":171,"description":172},"Configuration values","\u002Frunning\u002Fconfiguration-values","4.running\u002F08.configuration-values","Named values the application needs but must not contain — API keys, account numbers, thresholds.",{"title":174,"path":175,"stem":176,"description":177},"Your data","\u002Frunning\u002Fyour-data","4.running\u002F09.your-data","The Data tab — reading, correcting, adding to and clearing out what your application has stored, one environment at a time.",{"title":179,"path":180,"stem":181,"description":182},"Visitors","\u002Frunning\u002Fvisitors","4.running\u002F10.visitors","Who is using the application, counted without identifying anybody and with nothing to set up.",{"title":184,"path":185,"stem":186,"children":187},"Workspace","\u002Fworkspace","5.workspace",[188,192,197,202,207,212,217],{"title":189,"path":185,"stem":190,"description":191},"Your workspace","5.workspace\u002Findex","What every application in it shares — the domain, the design systems, the people, the user directory and, if you want it, one set of records — and how to be in more than one.",{"title":193,"path":194,"stem":195,"description":196},"People and roles","\u002Fworkspace\u002Fpeople-and-roles","5.workspace\u002F1.people-and-roles","Three roles, what each can do, how they apply to the builder as well as to the buttons, and why they belong to a workspace rather than to an account.",{"title":198,"path":199,"stem":200,"description":201},"More than one workspace","\u002Fworkspace\u002Fmore-than-one-workspace","5.workspace\u002F2.more-than-one-workspace","Belonging to several, switching between them, the role you hold in each, and why nothing crosses over.",{"title":203,"path":204,"stem":205,"description":206},"Organising applications","\u002Fworkspace\u002Ffolders-and-organising","5.workspace\u002F3.folders-and-organising","Folders on the dashboard, and how to keep a growing list navigable.",{"title":208,"path":209,"stem":210,"description":211},"Your own design systems","\u002Fworkspace\u002Fyour-own-design-systems","5.workspace\u002F4.your-own-design-systems","Authoring a design system for your brand, or a client's, by importing guidelines, a website or a Figma library.",{"title":213,"path":214,"stem":215,"description":216},"Your profile","\u002Fworkspace\u002Fyour-profile","5.workspace\u002F5.your-profile","Your name and how you are addressed, your password, your picture, two-step sign-in by email or text, and the theme.",{"title":218,"path":219,"stem":220,"description":221},"Where records live","\u002Fworkspace\u002Fwhere-records-live","5.workspace\u002F6.where-records-live","One store per environment, one across an application's environments, or one the whole workspace shares — what each costs you, and how to change it.",{"title":223,"path":224,"stem":225,"children":226},"Developers","\u002Fdevelopers","6.developers",[227,231,236],{"title":228,"path":224,"stem":229,"description":230},"For developers","6.developers\u002Findex","What is actually generated, and what to do when you inherit one.",{"title":232,"path":233,"stem":234,"description":235},"What gets built","\u002Fdevelopers\u002Fwhat-gets-built","6.developers\u002F1.what-gets-built","The stack, the shape of the repository, and the parts the platform provides rather than the application.",{"title":237,"path":238,"stem":239,"description":240},"Taking one over","\u002Fdevelopers\u002Ftaking-it-over","6.developers\u002F2.taking-it-over","For the developer who has just been handed an application built here.",{"title":242,"path":243,"stem":244,"children":245},"Reference","\u002Freference","7.reference",[246,249,254,259],{"title":242,"path":243,"stem":247,"description":248},"7.reference\u002Findex","Terms, limits, and what to do when something specific has gone wrong.",{"title":250,"path":251,"stem":252,"description":253},"Glossary","\u002Freference\u002Fglossary","7.reference\u002F1.glossary","Every term this documentation uses, in one place.",{"title":255,"path":256,"stem":257,"description":258},"Limits","\u002Freference\u002Flimits","7.reference\u002F2.limits","The boundaries that are real, so you do not discover them at an inconvenient moment.",{"title":260,"path":261,"stem":262,"description":263},"Troubleshooting","\u002Freference\u002Ftroubleshooting","7.reference\u002F3.troubleshooting","Specific symptoms, and what each one usually means.",{"id":265,"title":29,"body":266,"description":32,"extension":495,"hidden":496,"meta":497,"navTitle":498,"navigation":499,"path":30,"seo":500,"stem":31,"__hash__":501},"docs\u002F1.start\u002F4.what-to-expect.md",{"type":267,"value":268,"toc":485},"minimark",[269,273,279,284,343,346,350,357,363,378,384,388,398,412,422,428,432,435,441,447,453,459,463,466,482],[270,271,272],"p",{},"Honest expectations, including the unflattering ones.",[274,275],"shot",{"alt":276,"caption":277,"name":278},"A finished application running on its own address: a proposals pipeline with totals across the top and proposals grouped by the stage they have reached.","What comes out at the end — an ordinary application on an ordinary address, with nothing of the platform visible in it.","built-app",[280,281,283],"h2",{"id":282},"how-long-things-take","How long things take",[285,286,287,299],"table",{},[288,289,290],"thead",{},[291,292,293,296],"tr",{},[294,295],"th",{},[294,297,298],{},"Roughly",[300,301,302,311,319,327,335],"tbody",{},[291,303,304,308],{},[305,306,307],"td",{},"Creating an application",[305,309,310],{},"Two minutes of answering questions",[291,312,313,316],{},[305,314,315],{},"The first build",[305,317,318],{},"5–20 minutes, depending on how much you asked for",[291,320,321,324],{},[305,322,323],{},"A small change",[305,325,326],{},"1–4 minutes",[291,328,329,332],{},[305,330,331],{},"A substantial feature",[305,333,334],{},"5–15 minutes",[291,336,337,340],{},[305,338,339],{},"Deploying to test or live",[305,341,342],{},"1–3 minutes",[270,344,345],{},"These are the times on a normal day. A build that has to install new packages\ntakes longer; one that hits an error and works its way out of it takes longer\nagain.",[280,347,349],{"id":348},"the-rhythm-that-works","The rhythm that works",[270,351,352,356],{},[353,354,355],"strong",{},"Small asks beat big ones."," Three messages that each change one thing produce\na better result than one message with eleven requirements in it, and when\nsomething comes out wrong you know which sentence caused it.",[270,358,359,362],{},[353,360,361],{},"React rather than specify."," You do not have to describe the application\nperfectly up front. Look at what came back and say what is wrong with it. This\nis faster and more accurate than imagining the whole thing in advance.",[270,364,365,368,369,373,374,377],{},[353,366,367],{},"Say what, not how."," ",[370,371,372],"em",{},"Salespeople should only see their own proposals"," is a\ngood instruction. ",[370,375,376],{},"Add a WHERE clause on owner_id"," is not — and if you knew that\nmuch, you would not be here.",[270,379,380,383],{},[353,381,382],{},"Be concrete about the thing that matters."," \"Make it look better\" produces\nsomething arbitrary. \"The stage column is too far right and the dates are\nunreadable\" produces the fix you wanted.",[280,385,387],{"id":386},"what-goes-wrong","What goes wrong",[270,389,390,393,394,397],{},[353,391,392],{},"It misunderstands."," Regularly, and usually because a sentence had two\nreadings. Say so plainly — ",[370,395,396],{},"no, I meant the owner of the proposal, not the\naccount manager"," — and it corrects with the whole conversation still in mind.",[270,399,400,403,404,407,408,411],{},[353,401,402],{},"A build fails."," It happens. The work is still saved, the failure is explained\nin a sentence, and ",[370,405,406],{},"continue"," usually gets past it. See\n",[409,410,67],"a",{"href":68},".",[270,413,414,417,418,421],{},[353,415,416],{},"It changes something you liked."," Ask for it back, or go to\n",[409,419,420],{"href":121},"an earlier version",". Every build is kept, so nothing is\never actually lost.",[270,423,424,427],{},[353,425,426],{},"It refuses."," Some things are genuinely outside what this platform does —\na different framework, a service that is not connected. It will say so rather\nthan pretend.",[280,429,431],{"id":430},"what-does-not-go-wrong","What does not go wrong",[270,433,434],{},"Worth knowing, because these are the fears people arrive with.",[270,436,437,440],{},[353,438,439],{},"You cannot lose work by forgetting to save."," Every build becomes a version\nautomatically, including the ones that failed or that you stopped.",[270,442,443,446],{},[353,444,445],{},"You cannot break the live application by building."," A build changes the\npreview. The live copy keeps running the version you deployed until you deploy\nanother one.",[270,448,449,452],{},[353,450,451],{},"You cannot ship something broken by accident."," A deployment builds the\nversion first and only moves the address once the new copy answers. A version\nthat does not build never replaces the one that is live.",[270,454,455,458],{},[353,456,457],{},"You cannot corrupt the live data from test."," Each environment has its own\ndatabase. They cannot see each other.",[280,460,462],{"id":461},"when-to-ask-a-person","When to ask a person",[270,464,465],{},"Some things are faster to ask us than to work out:",[467,468,469,473,476,479],"ul",{},[470,471,472],"li",{},"The application needs to talk to a system we have not connected.",[470,474,475],{},"You want it in a language other than the one it came out in.",[470,477,478],{},"A build has failed the same way three times.",[470,480,481],{},"Something about the result is wrong in a way you cannot describe.",[270,483,484],{},"Ask. It is not an admission of anything.",{"title":486,"searchDepth":487,"depth":487,"links":488},"",3,[489,491,492,493,494],{"id":282,"depth":490,"text":283},2,{"id":348,"depth":490,"text":349},{"id":386,"depth":490,"text":387},{"id":430,"depth":490,"text":431},{"id":461,"depth":490,"text":462},"md",false,{},null,true,{"title":29,"description":32},"xUFevInDJPM2HsasP3pFJhEY8tfNdao52Mvp9nLgOQg",[503,504],{"title":24,"path":25,"stem":26,"description":27,"children":-1},{"title":34,"path":35,"stem":39,"description":40,"children":-1},1793657361790]