Posts

Showing posts from November, 2026

An Australian app build in AUD: GST, ABN and the three decisions to settle on day one

You have an app idea, a budget that does not look like an Australian agency quote, and a studio in Seoul that says five days. The first thing that usually stops the project is not code. It is the question your accountant asks: "Will there be GST on this invoice?" Here is the order we recommend to Australian founders, and why it saves a week. GST and the overseas supplier A company in Seoul is not registered for Australian GST, so it cannot charge GST on its invoice. If you are registered for GST and you buy services from an offshore supplier, you generally account for the GST yourself on your business activity statement under the reverse-charge rules for inbound intangible supplies. Practically, that means the invoice needs both parties' names and addresses, a clear description of the service, the amount and currency, the date, and a line stating that GST is accounted for by the recipient. Ask your accountant to confirm the exact wording and the threshold that applies...

A white-label build partner in one person: adding apps to an agency without hiring

A design studio I work with gets the same request about once a month: a client wants an app. Not a website — an app with logins, payments, and a store listing. The studio can design it beautifully and cannot build it, and hiring two developers to sit idle between projects is not an option. That is the situation white-label development exists for. I have been on both sides of it, as the person quoting and as the person a client never hears about, so here is how it actually works when the partner is one person with an AI pipeline rather than an agency with a sales team. What white-label means in practice The client relationship stays with you. Your brand is on the proposal, the invoices, and the meetings. I build the thing, appear on calls as part of your team when that helps, and stay invisible when it does not. The deliverable arrives in your client's accounts, with documentation, so the handover is yours to make. The parts that make this work or fail are not technical: One n...

A five-day build is not the impressive part. The handover is.

Every small studio eventually gets the same request: a client wants a working product in two weeks, and the studio has designers, a project manager, and no one who wants to spend three months on backend work. There are two common answers. Hire for the project and let the hire go afterwards. Or say yes, subcontract to the first freelancer who replies, and spend the next six weeks managing something nobody can see. Both answers cost more than the invoice suggests. A third answer is duller: buy the build from a partner who only does builds, agree the scope and the price in writing, and take delivery in a form you can maintain. What "five days" actually means Five days is enough when the scope is small and honest: one form that really submits, sign-in with two roles, one integration with a system the client already pays for, an admin screen for ten cases rather than a hundred. It is not enough when "the app" turns out to be three products. Saying that before the qu...

What I decide in the first hour of an AI-built app, and what I never let the model touch

Most of the work I do now starts with someone else's app. It runs on their laptop, it demos well, and it has been sitting at "almost done" for three weeks. So before I ever open an editor on a client build, there are a few decisions I make in the first hour, and a few things I never hand to the model. What I decide before I open the editor Who is the first person allowed in, and how do they prove who they are? What is the smallest payment that has to succeed on day one? And where does the data live if the machine dies? Those three answers decide the shape of the build. If a client can't answer them yet, that conversation is the first day of work, not a formality before it. What I give the model, and what I keep I hand over boilerplate, forms, tables, API wrappers, migration scripts — the boring seventy percent. It is genuinely fast there, and charging a client for typing it by hand would be dishonest. What I keep is the wiring between services: auth domains, redi...

Ce que je trouve dans les vingt premières minutes d'une app IA presque finie

Quelqu'un m'envoie un dépôt avec ce message : « c'est fait à 90 %, il ne reste qu'à déployer ». Avant, je commençais par la liste des fonctionnalités. J'ai arrêté, parce que la liste des fonctionnalités, c'est justement la partie qui marche dans la démo. Ce qui décide si cette app peut encaisser une vraie carte, d'un vrai utilisateur, sans personne derrière l'écran, se trouve toujours aux six mêmes endroits. Voici la passe de vingt minutes, dans l'ordre, et ce que chaque constat coûte en jours. 1. La clé qui se trouve dans le bundle du navigateur Ouvrir la page déployée, afficher la source, chercher sk- , service_role , AIza . La moitié des apps construites avec Cursor ou Lovable que je reçois livrent une clé d'API au client, parce que la clé était pratique dans le fichier où l'appel a été écrit et que le framework intègre volontiers tout ce qui commence par VITE_ ou NEXT_PUBLIC_ . Ce n'est pas « risqué en théorie ». N'importe qui...

Was ich in den ersten zwanzig Minuten einer fast fertigen KI-App finde

Jemand schickt mir ein Repository mit dem Satz „zu 90 % fertig, ich muss es nur noch deployen". Früher habe ich mit der Funktionsliste angefangen. Damit habe ich aufgehört, denn die Funktionsliste ist genau der Teil, der in der Demo funktioniert. Die Dinge, die entscheiden, ob diese App eine echte Karte von einem echten Nutzer annehmen kann, ohne dass jemand daneben sitzt, liegen immer an denselben sechs Stellen. Hier ist der Zwanzig-Minuten-Durchgang, in dieser Reihenfolge, und was jeder Fund an Tagen kostet. 1. Der Schlüssel im Browser-Bundle Die deployte Seite öffnen, Quelltext ansehen, nach sk- , service_role , AIza suchen. Die Hälfte der Apps, die mit Cursor oder Lovable entstehen und bei mir landen, liefert einen API-Schlüssel an den Client aus — weil der Schlüssel in der Datei bequem war, in der der Aufruf stand, und das Framework alles mit dem Präfix VITE_ oder NEXT_PUBLIC_ brav einbettet. Das ist nicht „theoretisch unsicher". Jeder kann ihn lesen, damit Geld au...

What I find in the first twenty minutes of an "almost finished" AI-built app

Somebody sends me a repo with the message "it's 90% done, I just need it deployed". I used to start by reading the feature list. I stopped, because the feature list is the part that works in the demo. The things that decide whether this app can take a real card, from a real user, without a human watching, are always in the same six places. Here is the twenty-minute pass, in order, and what each finding costs in days. 1. The key that is in the browser bundle Open the deployed page, press view-source, search for sk- , service_role , AIza . Half the Cursor and Lovable apps I see ship an API key to the client, because the key was convenient in the file where the call was written and the framework happily inlines anything prefixed VITE_ or NEXT_PUBLIC_ . That is not "insecure in theory". Anyone can read it, spend on it, and the first evidence is usually an invoice or a quota mail. The fix is a server route and a rotated key — half a day. The reason it costs half...

The app was finished on Thursday. Apple let it in the following Wednesday.

Thursday, 11:40 p.m. The founder sends the link to two friends and then to me, and writes: "it works." It does. Sign up, add a thing, edit it, delete it, log out, log back in. No errors. Nine days of work, and the product is real. The next morning he tries to give it to the world. That is when the week begins. Not the coding week. The other one. The one nobody puts in a plan, because none of it appears in any tutorial about building an app: two accounts that must approve you, a company number that may not exist yet, a domain that needs to prove it is allowed to send email, a page of legal text that a store will not accept as "coming soon", and a reviewer in another timezone who has ten minutes and no way to receive your text message. Here is what actually happened between "it works" and "anyone can install it", in the order it hurt. The number that takes a month He wanted to publish under his company. That means an organization account, and Apple...

Twenty tabs, twenty prototypes, zero apps on anyone's phone

Twenty tabs. Twenty prototypes. Not one app on anyone's phone. There is a new kind of stuck, and it arrived quietly over the last two years. Making a prototype used to be the hard part. It took a co-founder, a budget, or six months of evenings. Now you can describe an idea on a Monday and have something clickable before bed. That is genuinely wonderful, and it is also a trap, because the thing that became easy is not the thing that was stopping you. Ask around and you will find the same situation in a hundred laptops: twenty browser tabs, each holding a half-built app. One is a meal planner. One is a booking tool for a friend's business. One is the thing you were excited about in March. Every single one of them is at 80%. Zero of them have been used by a person who is not you. What is actually in the last 20% From the outside, 80% looks like "nearly done". From the inside, it is a stack of unglamorous doors that were never opened: A stranger's account - a confirma...

Sua ideia de app travou nos 80%. Em Seul, uma única pessoa acabou de lançar três.

  São 2 da manhã em Seul e alguém está olhando um projétil de tanque voar. Ele sobe por cima de uma colina, o vento empurra um pouco e cai exatamente na base do adversário. Do outro lado da tela tem uma pessoa de verdade, em outra cidade, que acabou de perder a rodada. Quem fez esse jogo escreveu a física, desenhou os tanques e redigiu a descrição na loja. Está sozinho na mesa às 2 da manhã porque é a hora em que os servidores ficam calados e ninguém manda e-mail. Conto isso porque quase todo mundo com uma ideia de app trava num lugar muito específico. E não é o lugar que a pessoa imagina. O muro dos 80% Você conhece esse muro. Abriu o Cursor, ou o Lovable, ou pediu um desejo ao ChatGPT, e por dois dias foi mágico. Apareceram telas de verdade. Uma página de login. Um botão verde bonito escrito «Pagar». Aí a mágica para. O app funciona no seu notebook mas não no seu celular. O botão de pagamento abre uma página dizendo 401. A loja devolve um print com um círculo vermelho desen...

Tu idea de app está atascada en el 80%. En Seúl, una sola persona acaba de lanzar tres.

  Son las 2 de la mañana en Seúl y alguien está mirando volar un proyectil de tanque. Sube por encima de una colina, el viento lo desvía un poco y cae justo sobre la base del rival. Del otro lado de la pantalla hay una persona real, en otra ciudad, que acaba de perder la partida. Quien hizo ese juego escribió la física, dibujó los tanques y redactó la ficha de la tienda. Está solo frente a su escritorio a las 2 de la mañana porque es la hora en la que los servidores están tranquilos y nadie manda correos. Te cuento esto porque casi todo el mundo con una idea de app se queda atascado en un lugar muy concreto. Y no es el lugar que cree. El muro del 80% Tú conoces ese muro. Abriste Cursor, o Lovable, o le pediste un deseo a ChatGPT, y durante dos días fue magia. Aparecieron pantallas de verdad. Una página de login. Un botón verde precioso que decía «Pagar». Y de repente la magia se acabó. La app funciona en tu portátil pero no en tu teléfono. El botón de pago abre una página que...

الساعة الثانية فجرًا ضغطتُ زر الإرسال — وظهرت اللعبة فعلًا على Google Play

في الثانية بعد منتصف الليل في سيول. ضغطت زر الإرسال في Play Console، وأغلقت الحاسوب، ونمت وأنا غير واثق. بعد ساعات، على Google Play في هاتفي، لعبة دبابات صغيرة اسمها Poktanwang — يمكن تنزيلها، وشخص لا أعرفه يلعبها بينما أنا نائم. ليست نسخة تجريبية: لا فريق عندي، لا مكتب، لا مستثمر، ولا مبرمج أتصل به عند الحاجة. فقط فكرة، وليالٍ طويلة، وعادة واحدة — أسأل الذكاء الاصطناعي، ثم أتحقق بنفسي من صحة الجواب. منذ ذلك الحين، السؤال الذي أسمعه أكثر من غيره: «عندي فكرة تطبيق، هل يمكن أن تصبح شيئًا حقيقيًا؟» الجواب: نعم، وغالبًا أسرع مما تتوقع. وقبل السعر، أجب: هل تشرح تطبيقك في جملة واحدة؟ من يدفع، ومقابل ماذا؟ ما الشيء الواحد الذي يجب أن يعمل من اليوم الأول؟ الاستشارة وعرض السعر مجانًا، قبل العقد صفر، عند العقد دفعة أولى فقط، والباقي بعد أن ترى النتيجة، وتعديلات مجانية. النسخة الكاملة: https://telegra.ph/الساعة-الثانية-فجرا-ضغطت-زر-الإرسال--وظهرت-اللعبة-فعلا-على-Google-Play-11-14 · الموقع: https://cpcai-studio.netlify.app/en/ · البريد: yyhak12345@gmail.com

ตีสอง ผมกดปุ่มส่ง — แล้วเกมที่ทำคนเดียวก็ปรากฏบน Google Play จริง ๆ

ตีสองที่โซล ผมกดปุ่มส่งบน Play Console ปิดแล็ปท็อป แล้วเข้านอนทั้งที่ไม่มั่นใจ ไม่กี่ชั่วโมงต่อมา บน Google Play ในมือถือของผมเอง มีเกมยิงรถถังเล็ก ๆ ชื่อ Poktanwang — ดาวน์โหลดได้ และมีคนที่ผมไม่รู้จักกำลังเล่นมันอยู่ตอนที่ผมนอนหลับ ไม่ใช่เดโม: ผมไม่มีทีม ไม่มีออฟฟิศ ไม่มีนักลงทุน ไม่มีโปรแกรมเมอร์ให้โทรปรึกษา มีแค่ไอเดีย คืนยาว ๆ และนิสัยอย่างหนึ่ง — ถาม AI แล้วตรวจเองว่าคำตอบนั้นถูกหรือเปล่า ตั้งแต่นั้น คำถามที่ผมได้ยินบ่อยที่สุดคือ "ผมก็มีไอเดียแอป ทำเป็นของจริงได้ไหม" คำตอบคือได้ และมักเร็วกว่าที่คิด ก่อนพูดเรื่องราคา ตอบสามข้อนี้ก่อน: อธิบายแอปให้คนที่เพิ่งเจอฟังได้ในหนึ่งประโยคไหม ใครจ่ายเงิน และจ่ายเพื่ออะไร หนึ่งอย่างที่ต้องทำงานได้ตั้งแต่วันแรกคืออะไร ปรึกษาและประเมินราคาฟรี ก่อนเซ็นสัญญา 0 ตอนเซ็นจ่ายแค่มัดจำ ที่เหลือจ่ายหลังเห็นผลงาน แก้ไขฟรี ฉบับเต็ม: https://telegra.ph/ตสอง-ผมกดปมสง--แลวเกมททำคนเดยวกปรากฏบน-Google-Play-จรง-ๆ-11-14 · เว็บไซต์: https://cpcai-studio.netlify.app/en/ · อีเมล: yyhak12345@gmail.com

2 giờ sáng, tôi bấm nút gửi — và game ấy thật sự xuất hiện trên Google Play

2 giờ sáng ở Seoul. Tôi bấm nút gửi trên Play Console, gấp laptop, và đi ngủ mà không chắc gì. Vài giờ sau, trên Google Play ở chính điện thoại của tôi, có một game bắn xe tăng nhỏ tên Poktanwang — tải được, và có người tôi chưa từng gặp đang chơi nó trong lúc tôi ngủ. Không phải bản demo: tôi không có đội nhóm, không văn phòng, không nhà đầu tư, không một lập trình viên nào để gọi khi bí. Chỉ có ý tưởng, những đêm dài, và một thói quen — hỏi AI, rồi tự kiểm tra xem câu trả lời có đúng không. Từ đó, câu hỏi tôi nghe nhiều nhất là: "tôi cũng có một ý tưởng ứng dụng, liệu có làm thật được không?" Câu trả lời: được, và thường nhanh hơn bạn tưởng. Trước khi nói về giá, trả lời ba câu: bạn mô tả ứng dụng của mình trong một câu được không? ai sẽ trả tiền, và trả cho cái gì? một việc gì bắt buộc phải chạy được ngay ngày đầu? Tư vấn và báo giá miễn phí, trước hợp đồng 0, khi ký chỉ đặt cọc, phần còn lại sau khi bạn xem kết quả, sửa miễn phí. Bản đầy đủ: https://telegra.ph/2-giờ-sáng-...

Pukul dua pagi. Saya menekan "Kirim" — dan game buatan satu orang itu muncul di Play Store

Sudah pukul dua pagi di Seoul. Saya menekan tombol kirim di Play Console, menutup laptop, dan tidur tanpa yakin. Beberapa jam kemudian, di Play Store ponsel saya sendiri, ada game tank kecil bernama Poktanwang — bisa diunduh, dan bisa dimainkan orang yang tidak saya kenal saat saya sedang tidur. Bukan demo: saya tidak punya tim, tidak ada kantor, investor, atau programmer lain. Hanya ide, malam-malam panjang, dan satu kebiasaan — bertanya pada AI, lalu memeriksa sendiri apakah jawabannya benar. Sejak itu, pertanyaan yang paling sering saya dengar: "saya juga punya ide aplikasi, bisa jadi beneran nggak?" Jawabannya: bisa, dan biasanya lebih cepat dari yang dibayangkan. Sebelum bicara harga, jawab dulu tiga ini: bisa kamu jelaskan aplikasimu dalam satu kalimat ke orang baru? siapa yang membayar, dan untuk apa? apa satu hal yang wajib jalan di hari pertama? Konsultasi dan penawaran gratis, sebelum kontrak 0, saat kontrak hanya DP, sisanya setelah kamu melihat hasilnya, revisi gr...

Your app idea is stuck at 80%. In Seoul, one person just shipped three.

  It is 2 a.m. in Seoul and someone is watching a tank shell fly. It arcs over a hill, catches the wind, and lands exactly on the other player's base. Somewhere in another city, a real person just lost that round. The person who made the game wrote that physics, drew those tanks, and typed the store description himself. He is alone at his desk at 2 a.m. because that is when the servers are quiet and nobody is sending emails. I am telling you about him because most people with an app idea get stuck in one very specific place — and it is not the place they think. The wall everyone hits at 80% You know the wall. You opened Cursor, or Lovable, or you typed a wish into ChatGPT, and for two days it was magic. Real screens appeared. A login page. A pretty green button that said Pay. Then the magic stopped. The app runs on your laptop but not on your phone. The payment button opens a page that says 401. The store reviewer sends back a screenshot with a red circle drawn on it. You clo...

From 80% to shipped: what a 3-5 day finish of an AI-built app actually looks like

Most AI-built apps are not missing features when they stall. They are missing verification. Something built with Cursor, Lovable, Bolt, v0 or Replit usually reaches a convincing demo fast: screens, flows, a database call or two. Then it sits at "almost ready" for weeks, because the demo ran on the builder's laptop against a preview environment, and every seam that crosses a file, an environment or a point in time was never checked. I finish those apps for a living. Not by rewriting them - by taking the code as it is, verifying the seams in the environment it will actually run in, and shipping. Here is what a three-to-five day finish looks like, day by day, so you can judge whether it fits what you are holding. Day 0 - a scope call that removes work The first call is not a sales call; it is a subtraction exercise. We pick the one job the app must do for its first paying user and list what will not be built this week. Anything that needs a bank contract, a telecom integrati...