[{"data":1,"prerenderedAt":332},["ShallowReactive",2],{"service-mobile":3,"service-mobile-related":123},{"id":4,"title":5,"body":6,"description":33,"extension":39,"eyebrow":40,"faq":41,"fromPrice":60,"headline":61,"includes":62,"meta":69,"navigation":70,"order":71,"path":72,"pillars":73,"priceNote":86,"related":87,"scales":90,"seo":96,"seoDescription":97,"seoTitle":98,"slug":99,"stack":100,"stem":119,"subhead":120,"tier":121,"__hash__":122},"services\u002Fservices\u002Fmobile.md","Mobile app",{"type":7,"value":8,"toc":32},"minimark",[9,14,18,22,25,29],[10,11,13],"h2",{"id":12},"what-a-starter-mobile-build-looks-like","What a starter mobile build looks like",[15,16,17],"p",{},"The $80k floor covers one platform, ten screens, auth and push and offline, a real TestFlight from week one, and App Store submission. Eight to twelve weeks. The point is a real app real users can install at the end of the build, not a prototype.",[10,19,21],{"id":20},"where-the-build-scales","Where the build scales",[15,23,24],{},"Second platform doubles a lot of work, including the API surface and the QA matrix. Real-time features (chat, presence, sockets) are a step change in backend complexity. Native modules each carry their own learning curve, especially camera pipelines and BLE. Subscriptions via RevenueCat are mostly mechanical but App Store review on a subscription is its own thing.",[10,26,28],{"id":27},"what-we-will-not-build","What we will not build",[15,30,31],{},"Webview-wrapper apps pretending to be native. Apps with no offline story. Apps that depend on a backend nobody is maintaining. Anything where the App Store will reject it on first submission and we can predict that from the brief.",{"title":33,"searchDepth":34,"depth":34,"links":35},"",2,[36,37,38],{"id":12,"depth":34,"text":13},{"id":20,"depth":34,"text":21},{"id":27,"depth":34,"text":28},"md","MOBILE APP DEVELOPMENT",[42,45,48,51,54,57],{"q":43,"a":44},"Native or React Native?","We choose per project. Native wins when the app is performance-bound or platform-bound. React Native wins when the surface area is broad and the team behind the app is mostly web. We tell you which one fits during discovery.",{"q":46,"a":47},"How long until App Store?","TestFlight in week one. App Store submission in week eight to twelve at the $80k floor, longer for two platforms or heavy native modules. Apple review usually adds three to seven days.",{"q":49,"a":50},"Do you do App Store optimization?","We write the first version of ASO copy at submission and pair with our SEO service for ongoing ASO work. See SEO.",{"q":52,"a":53},"What if we already have a backend?","We can build against it. Discovery includes reading the existing API contracts and identifying anything that needs to flex for the mobile use case.",{"q":55,"a":56},"How do you handle crashes?","Sentry from the first TestFlight. Symbolicated stacks, release tagging, and a real on-call rotation for the first 60 days post-launch (paid extra).",{"q":58,"a":59},"Can the app share a codebase with our web app?","With React Native, yes for business logic and data layer. UI is rarely shared cleanly across web and mobile so we don't try.","$80k","Native-feeling apps, App Store ready.",[63,64,65,66,67,68],"One platform (iOS or Android) at the $80k floor","Auth, push notifications, deep links, offline-friendly data model","Up to ten screens fully designed and built","TestFlight or Play Internal Testing build by week one","App Store \u002F Play Store submission and ASO copy","Two-week post-launch support window",{},true,50,"\u002Fservices\u002Fmobile",[74,77,80,83],{"title":75,"body":76},"Real performance, not Webview","Native or React Native, never a Webview wrapper. 60fps interactions where the device can support them. We measure on real phones, not simulators.",{"title":78,"body":79},"TestFlight in week one","A real install on a real device by the end of the first week. Every subsequent change is testable on TestFlight or Play Internal Testing before it ships.",{"title":81,"body":82},"Backend that scales with the app","We build the API alongside the app, not as an afterthought. Auth, push, offline sync, deep linking all in the codebase from day one.",{"title":84,"body":85},"Owned by you","Code, Apple Developer account, Google Play Console, signing certs. All transferred. You ship the next release without us if you choose to.","Phase-by-phase quote, fixed bid",[88,89],"saas","ai-integrations",[91,92,93,94,95],"Second platform (the other of iOS \u002F Android)","In-app purchases or subscriptions via RevenueCat","Real-time features (chat, presence, sockets)","Native modules (camera pipeline, AR, BLE peripherals)","Custom backend API with non-trivial business logic",{"title":5,"description":33},"Custom mobile app development for iOS and Android. Native Swift\u002FKotlin or cross-platform React Native. TestFlight in week one, App Store ready. Starting at $80k.","Mobile App Development | iOS and Android Apps Built to Ship | HARTECHO","mobile",[101,104,107,110,113,116],{"name":102,"note":103},"Swift \u002F SwiftUI","When iOS-first or iOS-only is the right answer.",{"name":105,"note":106},"Kotlin \u002F Compose","When Android-first matters.",{"name":108,"note":109},"React Native + Expo","When cross-platform is the cheaper path to the same UX.",{"name":111,"note":112},"Fastlane + EAS","One command to a TestFlight or Play build, every time.",{"name":114,"note":115},"Sentry + Datadog Mobile","Crash reporting and traces on real devices, not your laptop.",{"name":117,"note":118},"RevenueCat","In-app purchase and subscription management without the App Store headache.","services\u002Fmobile","iOS and Android, native or React Native. Built to ship to TestFlight in week one and to the App Store at the milestone you call it.","core","nSry_FXaafATDS4SqiGGO-UICQUpS6AV5kkEjpHaT-0",[124,228],{"id":125,"title":126,"body":127,"description":33,"extension":39,"eyebrow":151,"faq":152,"fromPrice":171,"headline":172,"includes":173,"meta":180,"navigation":70,"order":181,"path":182,"pillars":183,"priceNote":86,"related":195,"scales":197,"seo":203,"seoDescription":204,"seoTitle":205,"slug":88,"stack":206,"stem":225,"subhead":226,"tier":121,"__hash__":227},"services\u002Fservices\u002Fsaas.md","SaaS \u002F web app",{"type":7,"value":128,"toc":146},[129,133,136,138,141,143],[10,130,132],{"id":131},"what-a-starter-saas-build-looks-like","What a starter SaaS build looks like",[15,134,135],{},"The $60k floor covers a multi-tenant data model, auth with invites, Stripe billing, an internal admin scaffold, and one core feature loop fully built. Eight to twelve weeks. The point is to land at a working app one user could actually pay for, with the seams in place to grow from there.",[10,137,21],{"id":20},[15,139,140],{},"Multiple feature loops is the most common scaler. Each new loop usually touches the data model, the UI, billing, and admin, so the cost is not linear. Real-time collaboration is a step change in complexity. Public APIs and webhooks add their own contracts to maintain. Enterprise plans (SSO, SCIM, audit) are usually deferred to a separate phase.",[10,142,28],{"id":27},[15,144,145],{},"SaaS that bets the company on a feature no user has asked for. SaaS without billing. Apps where the founder cannot describe the first paying user. Anything where the build is the cheap part and the distribution is unsolved.",{"title":33,"searchDepth":34,"depth":34,"links":147},[148,149,150],{"id":131,"depth":34,"text":132},{"id":20,"depth":34,"text":21},{"id":27,"depth":34,"text":28},"SAAS DEVELOPMENT",[153,156,159,162,165,168],{"q":154,"a":155},"What stage of company is this for?","Founders going from spec to first paying customer, or teams whose v1 was built fast and now needs to actually work. We are not the right shop if you already have ten engineers shipping daily.",{"q":157,"a":158},"How do you split the build from the design?","Discovery and design phases come first. We do not write code against unsolved problems. Once the screens are signed off the build is mostly mechanical.",{"q":160,"a":161},"Can we hand off mid-build?","Yes. Every milestone is a working app. You can stop after design, after the first feature loop, or after launch and we hand off the codebase as-is.",{"q":163,"a":164},"Why Nuxt or Next instead of Rails or Django?","We are faster in TypeScript and the audience usually has TypeScript people on hand for the next hire. We will write Python or Rails for the right project but it is not our default.",{"q":166,"a":167},"How does enterprise stuff fit in?","SSO, SCIM, and audit logs are a real chapter, not a checkbox. We sequence them after product-market fit. Building enterprise-features-first is a common reason for SaaS projects to die.",{"q":169,"a":170},"What about AI in the app?","See AI integrations. Adding LLM features to an existing SaaS is its own scope. We will tell you when AI is the right shape and when it is not.","$60k","Multi-tenant apps, hand-coded.",[174,175,176,177,178,179],"Multi-tenant data model with org + user + roles","Auth (email + OAuth) and team invites","Stripe Billing with one to two plan tiers","Internal admin scaffolding for support and ops","Errors, traces, uptime monitoring at launch","One core feature loop (the thing the app actually does) end-to-end",{},30,"\u002Fservices\u002Fsaas",[184,187,190,193],{"title":185,"body":186},"Real auth, day one","Multi-tenant from the start. Roles, invites, audit trail. NextAuth or Clerk, with the seams in your codebase rather than a black box.",{"title":188,"body":189},"Billing that holds up","Stripe subscriptions, metered usage, proration, dunning. Tested against a real failure-case suite so you don't lose revenue to an edge case.",{"title":191,"body":192},"Admin from sprint one","An internal admin gets built alongside the app, not bolted on after support tickets start. You can see and edit every record in your data.",{"title":84,"body":194},"Schema, migrations, deploy keys, observability. All in your accounts. We work for you, the code does too.",[89,196],"internal-tool",[198,199,200,201,202],"Multiple feature loops with cross-team workflows","Real-time collaboration (presence, cursors, shared state)","Public API and webhook system for customer integrations","SSO, SCIM, audit logging for enterprise plans","Mobile companion app (see Mobile)",{"title":126,"description":33},"Custom SaaS and web app development. Multi-tenant architecture, Stripe billing, admin dashboards, integrations. Hand-coded in Nuxt or Next, owned by you. Starting at $60k.","Custom SaaS Development | Web App MVP and Beyond | HARTECHO",[207,210,213,216,219,222],{"name":208,"note":209},"Nuxt 3 or Next.js","SSR-first. Choice depends on your stack and your team.",{"name":211,"note":212},"TypeScript strict","Types derived from schema, no any escapes.",{"name":214,"note":215},"Drizzle or Prisma + Postgres","Migrations checked in, no manual schema drift.",{"name":217,"note":218},"NextAuth \u002F Clerk \u002F Better Auth","Multi-tenant patterns from day one.",{"name":220,"note":221},"Stripe Billing","Subscriptions, metered usage, customer portal.",{"name":223,"note":224},"Sentry, Datadog, Better Stack","Errors, traces, uptime. All set up at launch.","services\u002Fsaas","Web applications with real auth, real billing, real admin, real integrations. Built so the second hire on your team can actually read the codebase.","t8bDHNs9JzEHooUJw_GA9eJOhLDCTWQazFFWKtCJy-g",{"id":229,"title":230,"body":231,"description":33,"extension":39,"eyebrow":255,"faq":256,"fromPrice":275,"headline":276,"includes":277,"meta":284,"navigation":70,"order":285,"path":286,"pillars":287,"priceNote":86,"related":299,"scales":301,"seo":307,"seoDescription":308,"seoTitle":309,"slug":89,"stack":310,"stem":329,"subhead":330,"tier":121,"__hash__":331},"services\u002Fservices\u002Fai-integrations.md","AI integrations",{"type":7,"value":232,"toc":250},[233,237,240,242,245,247],[10,234,236],{"id":235},"what-a-starter-integration-looks-like","What a starter integration looks like",[15,238,239],{},"The $18k floor covers a single AI feature inside your app, with prompts, structured outputs, cost ceilings, an eval suite, and an observability dashboard. Two to four weeks. The point is the smallest feature that earns its keep, not a sweeping AI rebrand of your product.",[10,241,21],{"id":20},[15,243,244],{},"Adding features. Each new AI feature shares the eval harness and observability layer but has its own prompt design, output schema, and edge cases. Embedding pipelines over live data are a separate chapter (indexing, freshness, retrieval quality). Voice and vision change the cost and latency profile entirely.",[10,246,28],{"id":27},[15,248,249],{},"AI features whose job is to write your marketing copy in your own voice (use Claude directly, save the integration cost). AI features with no eval. Anything where the success criteria is \"feels smart\" instead of a measurable lift.",{"title":33,"searchDepth":34,"depth":34,"links":251},[252,253,254],{"id":235,"depth":34,"text":236},{"id":20,"depth":34,"text":21},{"id":27,"depth":34,"text":28},"LLM FEATURES IN YOUR PRODUCT",[257,260,263,266,269,272],{"q":258,"a":259},"How is this different from AI agents?","AI agents are a build, the whole product is the agent. AI integrations are a feature added to a product that already exists. Different scope, different floor price.",{"q":261,"a":262},"We already use ChatGPT internally. Why this?","That is sometimes the right answer. We tell you when it is. When the workflow needs to run inside your app on customer data with audit and cost control, an integration is the next step.",{"q":264,"a":265},"How quickly do you ship?","Two to four weeks from kickoff for a single integration at the $18k floor. Multi-feature integration work runs four to eight.",{"q":267,"a":268},"What if our data is sensitive?","Zero-retention modes on Claude and OpenAI by default. Self-hosted vector stores where compliance requires it. We design for the strictest data class in the system.",{"q":270,"a":271},"Can you work in our existing codebase?","Yes. We are comfortable in Next, Nuxt, Rails, Django, Laravel, and most TypeScript or Python stacks. We will ask for a read-only access window during discovery.",{"q":273,"a":274},"Do you maintain it after launch?","Two-week support window included. Beyond that we offer monthly retainers for model-update and eval-regression work, sized to the integration.","$18k","Add AI to the app you already have.",[278,279,280,281,282,283],"One AI feature wired into your existing app","Prompt scaffolding, structured-output schemas","Token budget and cost-ceiling enforcement","Eval suite with 20+ test cases against your data","Observability dashboard for token spend per session","Two-week support window after launch",{},40,"\u002Fservices\u002Fai-integrations",[288,291,294,297],{"title":289,"body":290},"Real data, real evals","We test against your data, not synthetic prompts. Eval suite ships with the integration so you can detect regressions on model swaps.",{"title":292,"body":293},"Cost-aware by default","Token budgets per request, cheapest-model-first routing, caching where the input shape allows. The bill stays predictable.",{"title":295,"body":296},"Inside your codebase","We add the feature to the app you have. No separate \"AI service\" your team has to maintain in parallel. The seams live with the rest of the code.",{"title":84,"body":298},"Prompts, evals, API keys, observability all in your accounts. We don't run anything for you after handoff.",[300,88],"ai-agents",[302,303,304,305,306],"Multiple AI features sharing a common eval harness","Embedding pipelines over large or live datasets","Voice or vision integrations (image generation, OCR, transcripts)","Fine-tuning or distillation onto cheaper models","Customer-facing chat with retrieval and tools (see AI agents)",{"title":230,"description":33},"Add AI features to an existing product. Smart search, summarization, generation, structured extraction. Hand-coded against your real data with cost ceilings and evals. Starting at $18k.","AI Integration Services | LLM Features for Your SaaS | HARTECHO",[311,314,317,320,323,326],{"name":312,"note":313},"Claude Opus \u002F Sonnet \u002F Haiku","Default. Routed by step based on cost and latency.",{"name":315,"note":316},"OpenAI \u002F Gemini","When the work calls for a second provider or a router pattern.",{"name":318,"note":319},"Postgres + pgvector","Embeddings, retrieval, semantic search in the database you already have.",{"name":321,"note":322},"Vercel AI SDK or direct Anthropic SDK","Whichever fits your existing app surface.",{"name":324,"note":325},"Langfuse \u002F Helicone","Trace every call, eval every output.",{"name":327,"note":328},"Inngest \u002F BullMQ","Background jobs for batch or long-running calls.","services\u002Fai-integrations","Smart search, summarization, generation, embedding-based recommendation, structured extraction. Wired into your existing codebase, evaluated against your real data.","-j0wBi04IhfAdX3TDzv1ND14cBJTY_C0VD3EccwE4CI",1779549900351]