/
2026-06-30 Community Meeting Notes

2026-06-30 Community Meeting Notes

 

Date

30 Jun 2026

Recording:

 

Antitrust Statement and Code of Conduct

antitrustandcoc.png
LF Antitrust/Competition Policy and Code of Conduct

The OpenWallet Foundation is committed to creating a safe and welcoming community for all. For more information please visit the

Code of Conduct.

Welcome and Introductions

Take the opportunity to introduce yourself or organization. Let the community know what interest you have in the Bifold effort.

Attendees

 

@Jason Leach <jason.leach@fullboar.ca>

 

Topics & Discussion

  • Cleanup and Migration

    • MVVM

    • Decouple UI from business logic

 

  • Arch. decisions are go go with MVVM, Decouple UI from business logic so that others can have more control to override the UI / UX components.

  • Bifold provides the utility to bridge mobile to credo.

    • Library.

  • OCA is too baked in. Decouple it?

  • Do docs / developer guides. To get developers all pulling the same direction we should get some more guides.

  • Developer new package and start moving the MVVM components in to it. While it would be opinionated, it would have the opportunity override and contain no navigation. Opinionated in what components / packages are used.

    • Question: Maybe we can start moving things out to a different package (strip core down) so we can continue to use the package name?

  • Mostafa proposed removing / cleaning up some dead components.

  • Christian: What are the components (building blocks) that we device / export for others to use to build out an application.

    • i.e. Credential Card

    • We need to add value. Cannot be to fat, cannot be too thin.

  • Jason: Ask Dave customizes several wallets, ask him what would provide the most value to a organization, new to bifold, that would give them the biggest boost to get off the running without going into “fork and forget mode”.

  • Mostafa: Bifold is missing allot of documentation. For example the how to use theming.

    • Do we do the documentation in a way that it’s very consumable by AI or focus on human implementers?

  • Recognize AI augmented developers are a thing going forward and we need to make Bifold compatible with developers using agents / AI to develop. Maybe this is 60/40 AI written.

    • Add some more notable agents.md with minimal viable instructions.

    • AI consumable documents are a thing.

  • We should have an AI policy. Most larger organizations have one. Jason to talk with Sean to see if LF has opinions.

    • We need to make sure that any output form AI is still understandable by People so that it can be maintained and worked on by people.

    • Make sure that any AI output is human understandable and maintainable. AI can often overcomplicate things.

    • While AI can write code, we need the code base to be “human understandable” first.

    •  

 

 

Action Items