📢 Monthly Checkup – Project Updates & Next Steps

[theperu]

Hey everyone! Here’s a recap of our latest meeting. Lots of exciting updates and improvements are on the way, and we’d love your input and contributions.

---

🚀 Project Growth & Updates

• GitHub: We’ve hit 1,000+ stars, and today, we briefly ranked 9th in trending repositories!
• iOS Downloads: We’ve surpassed 5,000 downloads, and at one point, we were ranked 7th in the Finance category in Italy—a great milestone!
• Android Downloads: We’ve also passed 3,000 downloads
• Next Steps: Our current priority is fixing bugs to reach a stable v1.0 release. While new features and improvements are exciting, they will be postponed until after we achieve this stable milestone.

---

📌 GitHub Project Boards & Organization

To better track and manage issues, we’re restructuring our GitHub project boards:

🔵 v1.0 Stable Board

• This board will track all issues that need to be resolved before the v1.0 stable release.
  • Any issue with the status “Backlog” means it is open for contribution. If you’re interested in working on it, leave a comment before starting so we can assign it to you.
• We may introduce difficulty labels on issues to help contributors understand the effort required before committing to them.

🎨 Design Team Board

• A dedicated board for the UI/UX design team will be added to help track ongoing design tasks and improvements.

🛠️ Technical Improvements Board

• This board will host issues related to improving the overall codebase, including:
  • Code formatting
  • Testing improvements
  • Database optimizations
  • Other technical enhancements

By organizing our work in this way, we hope to make it easier for contributors to find tasks that match their interests and skill level.

---

🛠 Testing Strategy

As we move toward v1.0, we need to establish a solid testing approach. Here’s the plan:

• End-to-End (E2E) Testing: A first draft PR will be submitted soon to introduce E2E tests using Python and Appium.
• CI/CD Integration: We are exploring whether we can run these e2e tests automatically using GitHub Actions.
• Pre-commit Checks: We will probably implement Husky or something similar to enforce checks before commits, ensuring better code quality.
• Test Coverage Tracking: A tool might be added to measure and track test coverage, helping us identify untested areas.
• Future Testing Plans: After the v1.0 release, we will dedicate more time to refining our testing approach and discussing a testing philosophy for new PRs.

---

💻 Coding Standards & PR Guidelines

To maintain a clean and consistent codebase, we’re introducing the following standards:

• Dart Formatter: Code should be formatted using:

  dart run format .

• GitHub Action for Formatting: A GitHub Action will be set up to automatically check that PRs follow the formatting rules.
• PR & Issue Templates: We will adopt predefined templates for PRs and issues to improve clarity and structure. We are considering examples from React and Bruno and will choose 2-3 issue templates and one PR template.

---

📜 Changelog Improvements

To improve transparency and communication about changes in the project, we will introduce:

• A technical changelog to document updates and improvements in the codebase.
• A user-friendly changelog for release notes, making it easier for users to understand what’s new in each version.

---

❓ Q&A Highlights

Here are some key topics discussed during the meeting:

🔹 Can we integrate Open Banking APIs?

• Right now, no, because Open Banking APIs come with costs per request, which makes it impractical for us at the moment. We hope to explore this feature in the future when we have the resources.

🔹 Are you looking for new maintainers?

• Not exactly. However, we may invite contributors to help with PR reviews, but without giving full repository permissions.

🔹 How can I contribute?

• If you’re a developer, start by looking at our GitHub issues. Find one that interests you, and comment on it so we can assign it to you.
• If you have less experience, look for issues labeled "good first issue", which are designed to be beginner-friendly.
• If you're a designer join the call on Thursday
• If you think you can help the project in a different way contact us and we'll talk about it.

🔹 Can we add a feature to import CSV files from other apps/banks?

• Yes! This would be a valuable addition. We might start with support for a few common formats and expand over time, it could even become a separate project.

🔹 Will there be a public roadmap?

• Yes. We are working on a public roadmap to outline our development priorities and plans and draft should be available in the docs soon.
• Additionally, we will create a document outlining our core values and what we are not willing to compromise on.

🔹 Should we introduce pair programming sessions?

• We think this is a great idea! We will:
  • Create a dedicated role for pair programming: Code Buddy.
  • Consider recording development sessions to help contributors understand the repo and our workflow.

🔹 Can we have a dedicated dev chat?

• Yes! We will create a new channel specifically for developer discussions.
• We will also set up another channel for pair programming.

🔹 Should we have dev-focused meetings?

• Yes, we plan to hold meetings dedicated to topics like database improvements, refactoring, and other technical discussions.

---

💬 Final Thoughts

We’re making fantastic progress 🚀 Now is the perfect time to get involved, whether by fixing bugs, improving tests, or contributing to discussions.

Got any questions or suggestions? Thanks for being part of this journey. 💙

[mikev-cw]

Thank you Marco.

Additionally, we will create a document outlining our core values and what we are not willing to compromise on.

I can take care of that