Delivering AppKernia source: versions, licenses, and maintenance ownership
Organize the public baseline, project patches, runtime credentials, and acceptance evidence so another team can take over and upgrade the project.
Read article
Four checks before adopting an AppKernia native module
Evaluate the purpose, dependencies, platform prerequisites, credentials, and evidence for secure storage, push, authorization, and CAPTCHA modules.
Read article
Publishing a UTS native module: interfaces, dependencies, and acceptance
Turn project code into an adoptable source package with a secure-storage example, clear paths, failure scenarios, platform evidence, and upgrade notes.
Read article