Former Service Offerings
CodeKing delivered web design, iPhone app development, custom scripts and CMS solutions from 2006 to 2014. The studio ceased client work in 2014 and now hosts a technical notebook.
what services did codeking provide between 2006 and 2014?
During the eight‑year run the studio focused on web design and iPhone application development. Projects ranged from full‑site layouts to native mobile interfaces, each built to match a client’s brand and functional requirements. The work also included bespoke scripts that extended platform capabilities and content‑management systems that let customers maintain their own sites without developer intervention.
Beyond visual and interactive work the studio handled licensing of proprietary components and delivered custom software packages tailored to niche business processes. Those engagements required close collaboration with clients to integrate third‑party APIs and ensure compliance with licensing terms. The resulting solutions formed the core portfolio that attracted repeat business throughout the period.
how did codeking structure its service offerings?
Service contracts were organized around defined phases: discovery, design, implementation, and handover. Each phase produced tangible artefacts such as wireframes, style guides, source code repositories, and deployment scripts. This phased approach allowed the studio to manage scope, track progress, and provide clear milestones for clients awaiting deliverables.
Pricing reflected the effort required for each phase and the complexity of the underlying technology stack. Custom scripts and CMS integrations were billed separately because they often involved bespoke logic and ongoing maintenance. Licensing work carried its own fee structure, accounting for both the initial purchase and any required support.
why did codeking stop offering client services?
In 2014 the studio decided to close its client‑facing operations and repurpose the website as a knowledge base. The shift was driven by a desire to focus on experimentation, measurement, and the publication of reproducible code rather than on delivering finished products for external customers.
The decision also reflected broader changes in the development ecosystem, where open‑source tools and AI‑assisted workflows reduced the need for small‑scale agency work. By turning the site into a notebook, the former team could share real‑world findings with developers who ship software daily.
what kind of content is available on the current codeking notebook?
The notebook now hosts technical notes, coding experiments, and concrete examples of AI integration into standard development pipelines. Each entry includes the problem statement, the method used, measurement data, and the exact code that was executed, allowing readers to reproduce the results on their own machines.
Older entries are archived to show the evolution of the studio’s interests. Those archives contain the original project write‑ups, screenshots, and code snippets that illustrate how web design and mobile development practices have changed over the years.
how can developers use the codeking archive for their own projects?
Developers can browse the archive to find ready‑to‑run code samples that solve common problems such as API authentication, data parsing, or UI component composition. Each sample is accompanied by a brief explanation of why a particular approach was chosen and what trade‑offs were observed during testing.
The notebook also documents measurement techniques, like timing critical sections or profiling memory usage, so readers can adopt the same metrics in their own workflows. By following the documented steps, developers can reduce guesswork and accelerate the shipping of reliable features.
where can I find references to past codeking projects?
The reference section lists completed projects, linking to the original deliverables, client screenshots, and any public code repositories that were released. Although the studio no longer provides services, the references serve as a historical record of the types of solutions that were built during the active years.
Each reference entry includes a short narrative describing the client’s challenge, the technical stack used, and the outcome of the engagement. This context helps readers understand the practical constraints that shaped the code and design decisions made at the time.
Questions
Are services still offered?
No, the studio closed its service operations in 2014. The site now serves as a technical notebook.
What is the purpose of this site?
The site documents methods, measurements, and code used when building software with AI.