A connected body of work
F2i is an independent software lab built by Lance. The work spans user-facing business applications, local AI orchestration, portable app tools and the lower-level technologies underneath them. The projects are connected where that creates a useful capability, not presented as an all-or-nothing bundle.
The central idea is to make the path from an interface to useful work easier to understand. A form can become a record and a workflow. An editable app can gain a private backend. A local model or phone event can become part of an operational system. Each step should have a clear owner and a visible boundary.
Practical principles
Keep application source editable where the format supports it. Make local processing an option rather than assuming that every task belongs in a remote service. Expose the implementation and the relevant test evidence so developers can evaluate the actual system.
Be explicit about maturity. Public beta, hardware beta and research experiments are different stages. A demonstration is valuable evidence of one working path, but it should not be promoted into a claim about every deployment. The project pages describe both capabilities and limits.
Not every public repository is open source
SoftN, OAIY and ZIPP identify Apache-2.0 source licensing; XDB uses MIT. FormLogic is proprietary, source-available software with restrictions on paid redistribution and third-party hosted or managed offerings. Aokie is proprietary software. Research and example assets may have additional notices.
Public source makes inspection possible. It does not, by itself, grant unlimited redistribution or commercial hosting rights. Read the actual project licence and asset notices for the intended use. This overview is not a replacement for those terms.
Follow the work at the source
The repositories contain documentation, releases and implementation history. Product sites provide their own demos and setup material. This F2i site connects those resources with an overview of the roles, use cases and architectural choices.
For a reproducible bug report, identify the project, version, environment and the smallest steps that show the problem. Do not publish credentials, private records or sensitive security details in a public issue. Follow the relevant repository’s security policy instead.