Minutes: #Organization Team Meeting (2026-04-13)

🚀 WG སྡེ་ཚན། CommOps WG
1

Meeting Date: Mon Apr 13 2026
Source: Google Doc Link

Summary

Masterclass preparations advanced with Ratna partnership and Vibu app release garnered substantial feedback with numerous bugs and features suggested.

  • Masterclass and App Release
    The in-person masterclass date was finalized in collaboration with Ratna, with an expected attendance of 100 to 200 people depending on funding. The Vibu app was released, with users from Tupisaka and influencers scheduled to join on the 19th for feedback.

  • Initial App Feedback Collected
    Participants reported multiple functional bugs, including a black screen after adding 5 plans and verses not displaying in some plans. Users also suggested content improvements, such as ensuring main emotion status items function as folders and simplifying the interface for daily prayers.

  • Usability and Retention Concerns
    Multiple localization issues were reported, along with accessibility concerns regarding white text on a yellow background for missing thumbnails. Concerns were raised about user retention for the year-long Abidharma challenge due to missing content and non-working features, suggesting gamification be incorporated.

Next steps

  • Remove Email: Remove old loadtaker.ai email addresses.
  • Call Members: Call working group members who were not present for follow-up.
  • Coordinate Localization: Get in touch with management to find someone who can localize Tibetan and Chinese app versions.
  • Report Bug: Send the specific verse and plan details about the missing verse bug to the Discord channel.
  • Document Feedback: Add screenshots and simple written explanations of reported app bugs to the shared Google Docs document.
  • Test Mac: Test app installation and functionality on Mac systems.
  • Submit Feedback: Continue testing the app. Fill shared Google Docs with suggestions, feedback, and problems.
  • Modify Login UI: Replace the existing cross button on the login screen. Implement a Skip or Sign In Later option instead.

Details

  • Initial Administrative and Update Requests: Tenzin Kaldan and Tashi Tsering discussed account management, specifically the com ops manager account, and Tashi Tsering requested all participants remove their load taker.ai before the meeting. They also emphasized that the discussion would be conducted in English. Additionally, Tashi Tsering asked participants to invite working group members who were not present to the meeting.
  • Masterclass and Course Updates: Tenzin Palkyi reported on a promising discussion with three Ratna people regarding an in-person masterclass. They finalized the date for the event, which includes polishing the marketing for the Dharma course by May 15th, followed by two weeks of customization, before making the course public. The expected attendance for the in-person masterclass is 200 people if Bharti funding is secured, and 100 people otherwise, collaborating with Ratna.
  • App Release Calendar and Collaborations: Evan Yerburgh provided an update on the app release, which occurred a few days prior to the meeting. They stated that on the 19th, users from the Tupisaka community and some influencers will come on board to provide feedback. The plan includes a release to the Chippy Taka community on May 1st, coinciding with Buddhapura in India, which will include the Abidharma in a Year and the Dharmabada in a Year programs.
  • Feature Development and Analytics: Evan Yerburgh noted that the team is focusing on improving user experience to get the minimum levelable product ready. They mentioned that Tamden and Kokashi have installed the Firebase SDK, and they expect to have a bot within a week that will post daily active users and download counts in the developer and team Discords. The next planned app release is the Charitara in a Year program on May 31st, coinciding with Suker Duchen and Vak day for Thailand.
  • Beta Testing and Workshop Updates: Yash Dixit reported they had updated the April calendar and were working on future activities regarding the Abidharma. They created beta testing guidelines which were sent to selected participants, many of whom expressed enthusiasm about collaborating. Yash Dixit also worked with Pela on selecting trainers for upcoming workshops.
  • Call to Action for App Download and Feedback: Tashi Tsering outlined the primary goal of the meeting: for everyone to download and start using the new Vibu app on their devices. The intention was to gather feedback, including bug reports, surprising features, and suggestions for future improvements, with Tashi Tsering requesting that those who typically speak less be prioritized for feedback. drongbu lobsang, who could not bring a phone, checked if they could download the app on a Mac laptop.
  • Initial App Feedback and Bug Reports (Design/Content): Early feedback noted several issues, including the lack of thumbnail images for certain topics like Aspiration and Joy, which Evan Yerburgh confirmed was a universal issue. drongbu lobsang also suggested that main emotion status items, such as Anger, should function as folders containing simple plans, rather than being plans themselves. Furthermore, Tenzin Noryang found that the English version displayed Tibetan commentary for some phrases, which Jay Yeshe Gyatso explained was due to missing English versions.
  • Feature Suggestions (User Experience and Content): Users suggested features to enhance the app’s appeal, such as adding a Tibetan astrology feature. Karma Tashi suggested simplifying the interface for accessing daily prayers and mantras, proposing a “Featured Prayers” section on the home screen instead of the currently lengthy routine builder. Gyaltsen Dhargyal proposed an option for users to create separate groups or lists for prayers, such as morning and evening practice, within the Nyamlin feature, as currently the list is only one long compilation.
  • Technical and Usability Bugs/Concerns: Several bugs were reported, including one where the whole screen went black after Tenzin Palden added five plans to a single time block, requiring an app refresh. Jay Yeshe Gyatso reported a bug where verses were not displaying in some plans despite being connected in the We Buddhist Studio. Tenz Kuns noted issues with creating a routine, where deleting the only time block resulted in an error when trying to click “Done,” and that the default back button did not function. Tashi Tsering highlighted that the “Play” button should not be visible for recitations that do not yet have audio, as clicking it results in a “coming soon” message.
  • Localization, Design Consistency, and Accessibility Concerns: Norbu Tsering observed that the dashboard felt “box-like” and lacked personalization, suggesting elements like rotating words or a personalized greeting to improve engagement. Concerns about localization included inconsistent or missing text/elements in the Tibetan version, such as missing parts in the Yimuk section. Menla Tsomo raised an accessibility issue regarding the use of white text on a yellow background for thumbnails that fail to load, noting that this combination is difficult for people with color blindness to read.
  • User Engagement and Retention Concerns: Tenzin Palkyi expressed concern about the user retention for the Abidharma in a Year challenge, citing currently non-working play buttons, missing commentary, and a non-functional “Ask AI” feature. Tenzin Palkyi suggested incorporating gamification or micro-surveys, like asking for daily intentions, to keep users engaged and motivated throughout the year-long plan, which currently feels “dull”. The app team is currently loading the Firebase SDK, which will help track daily active users but not specific plan enrollment numbers.
  • Interface and Usability Improvements: Tenzin Kaldan suggested that the notification sound should be unique to the app. They also suggested that the routine view could be improved by only showing the time block card, and users would click the card to see the full list of routines, which would improve the user experience. Tenzin Kaldan also reported an annoying issue where trying to select text for translation takes the user to the beginning of the text instead of the desired segment.
  • Repetitive Login Questions and Troubleshooting: Tashi Tsering noted that every time they deleted and reinstalled the app, the system repeatedly asked them personal questions (such as religion) even though they had logged in and answered them previously. They attempted to resolve this by deleting, reinstalling, signing in, and logging out, but upon the next login attempt, the repetitive questions reappeared. This behavior suggests a potential issue with how user data persistence is being handled during app reinstallation and log-in.
  • MacBook App Functionality Issue: Tashi Tsering reported a separate problem when using the app on a MacBook, stating that after downloading it through the App Store, the application would only display the initial loading screen—a red circle with the logo—and would not proceed further. They explicitly requested that the team conduct testing on the Mac platform to address this issue.
  • Call for Continued App Testing and Feedback Submission: Tashi Tsering emphasized the importance of continued testing by all participants, instructing them to utilize the shared Google Docs to document all suggestions, feedback, and problems they encounter. The intention is to provide the development team with comprehensive data for review.
  • Feedback on Login Screen Design: Tenz Kuns offered feedback concerning the login screen, suggesting that the current “cross button,” which resembles a website close button, is unnecessary . They proposed replacing it with an alternative button like “skip” or “sign in later” instead .
  • Appreciation for Feedback Volume: Evan Yerburgh expressed gratitude to all participants, acknowledging that the feedback received was super useful and significantly exceeded their expectations. They recognized that there are now many things to work on to make the app better.