Technical publishing
KodeFrames technical books develop practical .NET engineering knowledge around resilient applications, cross-platform development, software architecture, and responsible AI-assisted workflows. Current titles remain in development, and publication links are added only when their destinations are verified.
Current titles
These titles already form part of the KodeFrames technical-publishing programme. Their scope and intended audiences are established, while public purchase and book-detail destinations remain withheld until verified.
Final title and subtitle intentionally withheld until publication readiness.
A practical guide to designing applications that remain useful during unreliable connectivity, with deliberate local data, synchronization, conflict, recovery, testing, and deployment strategies.
For: .NET developers, architects, technical leads, students, and teams building resilient desktop, mobile, and field applications.
Final title and subtitle intentionally withheld until publication readiness.
A structured approach to using AI throughout .NET MAUI development while preserving architecture, verification, technical ownership, maintainability, and responsible engineering judgment.
For: .NET MAUI developers, C# developers, freelancers, founders, consultants, educators, students, and software teams adopting AI-assisted workflows.
Publication status
The website distinguishes work that is actively being developed from material that has actually reached a verified public release.
Both listed books are currently represented as in-development titles. Their subjects, summaries, intended audiences, and technical direction can be described without presenting them as published.
Purchase destinations, publication dates, final cover assets, pricing, identifiers, and other release metadata are not presented until those details are established and suitable for public use.
Publishing approach
KodeFrames technical publishing is structured around implementation context, reasoning, verification, and material that developers can apply to real software work.
Book topics are connected to real software concerns such as architecture, local data, synchronization, cross-platform delivery, testing, deployment, maintainability, and responsible use of development tools.
Technical material should make important decisions and trade-offs understandable rather than presenting code or prompts without the engineering context needed to evaluate them.
Examples, workflows, terminology, assumptions, and platform guidance should be reviewed as technical content, not merely formatted as finished prose.
Publication state, purchase destinations, cover assets, identifiers, and other release details should appear on the website only when the underlying information has been verified.
Technical coverage
The two active titles cover complementary areas of modern .NET engineering, from resilient application design to disciplined AI-assisted development.
Local data, synchronization, conflict handling, recovery, unreliable connectivity, testing, and deployment strategies for software that must remain useful away from dependable networks.
Commercial desktop and mobile application development with C#, .NET, .NET MAUI, maintainable structure, platform-aware decisions, and practical delivery concerns.
Structured use of AI and prompt engineering while preserving technical ownership, architecture, verification, maintainability, and engineering judgment.
The design and validation practices that connect implementation decisions to maintainable software, dependable workflows, and controlled deployment.
Publication path
Publication readiness requires more than completing prose. Technical material, supporting assets, metadata, formatting, and public destinations all need their own verification.
Build the technical narrative, examples, explanations, workflows, and supporting material around a clearly defined audience and engineering purpose.
Check examples, terminology, architectural reasoning, platform assumptions, internal consistency, and the relationship between guidance and the software practices being described.
Complete the required formatting, metadata, cover assets, publishing files, and other release material without presenting unfinished elements as final.
Add public book and purchase destinations to the website only after the relevant publication state and destination have been confirmed.
Engineering knowledge
KodeFrames books are developed alongside software projects, engineering articles, architecture decisions, and developer-focused resources.