The Buzz— BeeWare

What we've done

We attended PyCon AU; video of the talk we gave on accessing phone hardware from Python is available on YouTube. We also had a very productive sprint - 9 contributors earned their challenge coin, for contributions ranging from corrections to the tutorial, to the addition of a dark mode flag to Toga. We also gave out one Yak Herder coin, for someone who helps other people to get their challenge coin. A huge thank you to everyone that came along and participated!
Our patch for Pillow isolating its build system from Homebrew when building on macOS has been finalised and merged. This is essential for iOS support, as it's easy for Homebrew macOS ARM64 binaries to leak into iOS builds; but it also has benefits for macOS builds.
We've completed work on modifications to the Pillow build system to support building for iOS. However, testing this work has revealed the need for additional changes to cibuildwheel and the upstream CPython support for iOS.
We've submitted a PR to cibuildwheel to add a test-sources configuration item. This feature is required for iOS testing, but can also be used on other platforms, so we've contributed it independently in order to make the iOS changes easier to test.
We've started work on some modifications to how the CPython iOS testbed project is run. This has become necessary because of a change introduced in Xcode 16, but in order to fix the problem, we'll also be able to improve the reporting of test output during a test run, and also make the test harness useful as a generic utility for any iOS project.
We've made good progress towards resolving a long-standing memory management issue in Rubicon. This change will remove almost all need for manual memory management of ObjC objects, making iOS and macOS development much more robust.
We resolved a number of CPython test stability issues on Android. In most cases, this wasn't an indicator of a broken feature, but of an unstable test - but as a result of the extensive testing done by CPython as a project, even a small instability can manifest as a semi-regular test failure.
We've started work on modifying Toga's web backend to be compatible with Micropython. This significantly reduces the startup time for a Toga app; we're hoping to be able to spend a lot more time on the web backend in the coming year.
We've formally taken on responsibility for restoring Emscripten to Tier 3 support in CPython, and reviewed a number of patches aimed at restoring Emscripten support.

What's next?

December will be a short month because of end-of-year holidays; we'll be continuing to work on binary packaging. The work we've done porting Pillow to iOS has revealed a number of gaps in the tooling needed to develop and test packages for iOS; so we will be working on getting that upstream tooling in place, using Pillow as a demonstrator for that work. Our overall goal hasn't changed - to get tools in place so that third-party projects can officially support iOS and Android - but it's become clear that there's a lot more upstream work required than we originally anticipated. However, we'll keep working toward this goal until creating packages for iOS and Android is as straightforward as any other platform.

We'll also be continuing to work on Python Emscripten support, and Toga's Web backend, with the eventual aim of getting the web backend to the same level of support as the other Toga backends.

Want to get involved?

Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:

Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.

What we've done

Most importantly, we released Briefcase 0.3.20 and Toga 0.4.8, including support for Python 3.13 - which includes the official support in Python for iOS and Android! This is a major milestone for BeeWare as a project, representing a significant portion of the work done over the last 12 months.
We've prepared an initial patch to cibuildwheel that is able to build and test simple iOS wheels. This patch isn't ready to submit upstream, but it is able to build simple iOS wheels.
We've submitted a patch to Pillow to isolate its build system from Homebrew when building on macOS. This is essential for iOS support, as it's easy for Homebrew macOS ARM64 binaries to leak into iOS builds; but it also has benefits for macOS builds.
We've made a number of improvements to multibuild, the tooling that Pillow uses to compile non-Python binary dependencies.
We've modified the CPython iOS testbed project so that it can be used as a testbed for any iOS Python project.
We've improved error reporting when Briefcase can't clone a template.
We've switched to using httpx instead of requests for Briefcase's internal download handling. This provides slightly better error handling, better options for improving HTTP/2 usage, and we're now consistently using httpx in Briefcase and in our example code.
We've modified Toga to lazily load components, rather than importing everything into the toga namespace at startup. This should improve application startup times, especially on platforms like mobile and web where this startup time is noticeable.
We resolved an issue causing intermittent test failures when testing Toga on Wayland.

What's next?

We will be continuing to work on binary packaging in November. We're using Pillow as a demonstrator for this work - it's a package that has a significant binary component, is widely used (including on mobile), but has a non-trivial build process (largely due to the non-Python binary dependencies). The hope is that by the time we're able to compile Pillow for iOS, we will have resolved many of the issues facing other binary packages. Our goal remains to have at least some third-party projects officially supporting iOS and Android by the end of the year, but this may be impeded by the sequence of dependencies that need to land and be published before upstream projects can accept iOS and Android patches.

We'll also be speaking at PyCon AU at the end of the month, including attending both days of the sprints. If you're able to make it to Narrm/Melbourne, we hope we'll see you there!

Want to get involved?

Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:

Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.

Q3 progress

In Q3 the biggest milestone we achieved was the finalisation of Tier 3 support for Android in CPython. The last of the compatibility and documentation issues associated with Android have been resolved, and Android buildbots are now running for both x86_64 and ARM64. Python 3.13.0 is due for release in about a week; we should be in a position to support this release very soon after the official release.

We've also made significant progress on binary packaging. We've backported all the Python 3.13 patches for iOS into BeeWare's support for Python 3.9-3.12, and we've updated our Mobile Forge infrastructure to generate binary wheels for a number of popular packages. We've developed iOS compatibility patches for pip and crossenv; these patches have been submitted and received initial reviews; we'll continue to work with those projects to land these patches upstream.

Q4 priorities

In Q4, we'll be focussing on the tools and documentation needed to for third-party Python packages to add Android and iOS support to their official CI and release processes. In addition to contributing to tools like pip and cibuildwheel, we'll develop the tools and documentation needed so that it is easy to add CI configurations for mobile platforms. The hope is that by the end of the year, there will be at least one third-party package that produces Android and iOS wheels without any direct involvement of the BeeWare team.

Longer term goals

Once we've got a strong story for packaging third-party packages for iOS and Android, we'll be able to turn our focus back to Toga, and the work needed to make iOS and Android compelling app development platforms. There's a number of navigation and data organization widgets that need to be developed; we also need to improve documentation of some common development patterns that are sources of common questions in BeeWare support channels.

There are also further improvements that we'd like to see in Python itself. This year we've been able to get Android and iOS to Tier 3 support; getting those platforms to Tier 2 is an obvious goal for future Python releases. We'd also like to contribute the tooling needed so that Python is able to distribute official binary releases of iOS and Android, and add an official macOS artefact that mirrors the "Windows embedded" installer. We've had discussions with the Python core team about how this could be achieved; over the coming year, we hope to land these changes.

What we've done

Android is now officially a Tier 3 platform in CPython! Over the last month, we've resolved a number of bugs that were preventing us from deploying a reliable buildbot for Android (on both x86_64 and ARM64); as a result, the CPython buildbot fleet now contains Android buildbots. The Android-related changes to documentation have also been merged; Python 3.13.0rc3 (due for release any day now) will incorporate all these changes.
We completed the updates to Mobile Forge to support the new official iOS wheel format, and published updated wheels in this format for the packages for which we have recipes. As part of these changes, we've also added CI checks to Mobile Forge.
We've submitted a patch to support iOS in pip. This patch also requires some patches to packaging and distlib that pip includes as vendored copies.
We've submitted a patch to crossenv that allows cross-compiling Python packages for iOS. There is some additional work required before this patch can land - crossenv's testing framework is currently broken, so it's not currently possible to verify changes in CI. We'll be working on restoring this testing support in the very near future.
We attended the CPython core team summit. During this week-long sprint, we were able to resolve a number of open questions about Python support on mobile, and begin planning for work that will hopefully be incorporated into the Python 3.14 release.
We released Toga 0.4.7, incorporating fixes for a number of bugs discovered in the recent 0.4.6 release, as well as some minor feature additions.
We transitioned Toga's GTK backend to use PyGObject's native asyncio support. This allowed us to deprecate Gbulb, the GTK asyncio plugin that we've been maintaining for several years.
We corrected an issue with the use of recent Textual versions in Toga, and added a bare-bones runtime test to ensure that the problem doesn't re-occur. This also required a fix for macOS console app testing in Briefcase.
We made some usability improvements to the rendering of Toga's documentation, and modified Toga's ReadTheDocs configuration to encourage search engines to return the stable documentation by default.
We modified the handling of Toga's app icons on macOS to improve compatibility with PyInstaller.
We corrected a number of issues with WebView handling, including ensuring that DOM storage is always available, and improving error handling when the WebView cannot be initialised on Windows.
We added protection against an edge case of asynchronous Task handling that could lead to the premature garbage collection of long lived tasks. We've also had some discussions with the CPython core team about fixing this problem in Python itself.
We spoke at PyBay on building mobile apps in Python.

What's next?

In October, we will continuing working on binary package support for mobile platforms. In addition to responding to any review feedback on the patches we've already submitted, we'll be working on new patches for cibuildwheel and meson-python, as well as tooling to make it easy for third-party libraries to run CPython test suites on mobile platforms. We should also be able finalise Briefcase's Python 3.13 support for Android, and start work on Android packaging. Supporting packaging for mobile platforms is a long term project which we expect to continue for several months; the hope is that by the end of the year, we will be able to contribute patches to third-party projects so that iOS and Android wheels become officially produced, rather than BeeWare-maintained artefacts.

Want to get involved?

Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:

Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.

What we've done

We've completed the process of backporting the CPython changes for iOS compatibility to Python 3.9 through 3.12. We've published support packages and stub binaries that incorporate these changes, and made the changes to Briefcase needed to support these new versions.
We've begun work on updating Mobile Forge and related binary tooling to support the new official binary tag and framework format required by the PEP-compliant patch for iOS support. So far, we're able to compile simple binary packages like lru-dict, and non-Python dependencies like libjpeg; we're working on restoring binary support for more complex binary dependencies.
We've landed the Android test runner script, fixed a number of issues that have arisen in CPython's Android support since the original patches landed, and deployed an Android CPython buildbot. This buildbot has revealed some edge cases (primarily in socket and signal handling) that only appear to manifest under the unusual load conditions generated by a buildbot; so, we've temporarily disabled the buildbot while we investigate the cause of these problems.
We completed work on a new API for document-based apps.
We completed work on an API for status icon apps.
We released Toga 0.4.6. This includes the support for document-based apps, status icon apps, and a number of other long-awaited features, such as apps without menubars, available in a stable release.
We updated the support for WebView on Windows to a more recent version, and resolved an issue with compatibility with Windows Store Python.
We diagnosed and contributed fixes for a number of issues in tools that BeeWare depends on for our build tooling. This includes updates to CI configurations to support Sphinx 8, fixes for Sphinx 8 support in a Sphinx plugin, and diagnosing issues with a recent Towncrier update.
We presented a keynote at Kiwi PyCon on the future of Python.

What's next?

In September, we'll be continuing work on binary package support for mobile platforms. Once we've restored support for binary wheels using the new binary tag and framework format, and added support for Python 3.13, we'll start upstreaming the changes we've made so that the wider Python ecosystem can start supporting iOS and Android. We'll also start working on the fixes to tools like pip, cibuildwheel, and meson-python that need to have explicit iOS support. We expect that this work will be ongoing for several months, but some of the work should be submitted upstream for review by the end of the month.

We'll also be presenting at talk at PyBay in San Francisco on mobile app development in Python, followed by the CPython core team sprint.

Want to get involved?

Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:

Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.

What we've done

We've resolved a number of issues with iOS and Android compatibility in CPython 3.13. Although patches for iOS and Android compatibility landed months ago, a number of changes have been landed since then which have inadvertently broken compatibility with these platforms. These issues usually indicate a subtle issue with the implementation of the feature that has been added - but diagnosing and correcting the source of the problem can often take days. There have also been some small improvements made to the iOS patches, such as a configuration option ensuring App Store compliance for both iOS and macOS.
We've begun the process of backporting the CPython changes for iOS compatibility to the older supported CPython releases. So far, we've completed the port to 3.12, and the 3.11 port is mostly complete; backports for 3.10 and 3.9 should be underway shortly. This includes significant changes to the Python-Apple-support repository, switching the build of the macOS support package to be based on the official CPython download, and adding a CI test suite that can be used to simplify the process of making a new release.
We've almost completed adding a test runner script for Android. This will form the basis for an Android CPython buildbot in the very near future.
We've added support for using an externally managed libmpdec implementation to the iOS patch. This is a change that was recently introduced to CPython, and will become required in CPython 3.15.
We've almost completed work on a new API for document-based apps.
We've developed an initial design and prototype for status icon apps.
We've added an API to make it easier to add and remove commands from a Toga app.
We corrected an issue that was causing intermittent Toga CI failures on macOS.
We've improved Briefcase's validation of the version of Git that a user has installed.
We've corrected an issue with the way macOS signs apps. This was causing problems with apps that have particularly complex application layouts.
We've modified Briefcase to use the newly available "stripped" Python Standalone binaries on Linux.
We've improved the validation of document type declarations in a Briefcase project.

What's next?

In August, we'll be continuing preparations for the upcoming Python 3.13 release, and working on the mobile Python binary packaging ecosystem. The initial release candidate for Python 3.13 will be released very soon; with any luck, this means there should be less inadvertent breakages to diagnose, so we can focus on improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.

We'll also be at Kiwi PyCon, presenting a keynote about the future of Python.

Want to get involved?

Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:

Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.

Q2 progress

The biggest news for the quarter is that iOS is now officially a Tier 3 supported platform in CPython. All the patches required for iOS compatibility have been landed, and a buildbot is in place; as of 3.13.0b1, CPython will build for iOS without any patching. Android support is close behind; the only missing piece is the buildbot.

We made some major improvements to the BeeWare tutorial, adding sections on customization of the packaged app, and handling permissions for apps. We were able to use these changes as part of a well-received tutorial at PyCon US. We also ran a very successful booth and sprint at PyCon US.

We also completed a lot of improvements in Briefcase and Toga, expanding the types of apps that can be supported. Briefcase can now package console apps; and Toga now has an official API for apps that don't have menu bars, background apps, and apps that aren't governed by the lifecycle of a single "main" window. These have been the subject of long-standing feature requests (some of them almost as old as Toga itself), so it's great to be able to finally address these limitations.

The one area where we weren't able to make an progress was in packaging for mobile platforms. However, we did have some very productive discussions at PyCon US, so we're confident we'll be able to make good progress on this in the coming quarter.

Q3 priorities

The highest priority for Q3 is to get ready for the Python 3.13 release in early October. This involves finalising the work on the Android buildbot so that Android is officially Tier 3; preparing Briefcase and the Python builds that BeeWare supports to be ready for the 3.13 release; and doing as much work as we can on the packaging ecosystem so that package maintainers can publish wheels for iOS and Android.

We'll also be attending Kiwi PyCon in August, and attending the Python Core Team summit in September.

Longer term goals

Getting the Python ecosystem to support iOS and Android is requires a lot more than just adding patches to CPython and some related tools. There will be a lot of education and support work required to help the community adopt iOS and Android; and there is certain to be ongoing maintenance as Python and the platforms evolve. There are also many ways that Python mobile support could be made even better, including the publication of official iOS and Android binaries, and potentially getting to Tier 2 (or even Tier 1) support.

There's also a lot of work that can be done to Toga to make iOS and Android compelling platforms to develop for. Toga is still missing some key widgets to support navigation and data organization; and even when these widgets exist, there will be a need for documentation and examples to demonstrate how to build apps for these platforms. We anticipate we'll be looking at these towards the end of the year. We also anticipate that we'll start looking more seriously at Toga's web backend, attempting to bring it to a level of support comparable to the desktop and mobile platforms.

Summary

It's been another busy quarter with a lot of progress, but as always, there's still plenty to do. Completing official support for iOS and Android means the foundational work needed to support mobile platforms will be complete; we can then focus on what we - and the community - build on that foundation.

What we've done

We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
We modified Briefcase to distribute the stub binaries as standalone artefacts, rather than including them in the app template. We also significantly optimised how Briefcase uses templates. Between these two changes, the download size required for a first project on macOS has been reduced from around 200MB, to less than 4MB.
We isolated Briefcase's use of Cookiecutter so that all of Briefcase's cached content is contained in Briefcase's own cache folder.
We added support for distribution certificates on macOS.
We modified Toga's APIs to use namedtuple types for Size and Position references.
We corrected a number of stability issues with Toga's testbed CI, and added CI testing for Wayland on Linux.
We completed a major overhaul of typing in Toga's API surface.
We added support for conditional coverage in Toga's testing. It is now possible to get a clean coverage report without running the test suite on every Python version and every platform.
We added an official API for customizing the system-installed menu items.
We added an API for detecting the screens available for an app to use, and for setting the position of windows relative to those screens.
We added support for "simple" apps - apps that don't have menu bars.
We added support for apps whose lifecycle isn't tied to a single "Main" window, such as background apps (apps that don't have any windows) and document-based apps.
We added support for app modal dialogs.

What's next?

Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.

Want to get involved?

Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:

Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.

What we've done

We attended PyCon US. We presented on the state of mobile support in CPython to the Language Summit; we presented a tutorial to over 30 attendees; we ran a booth in Community Row; we presented a talk on writing a data visualisation app with BeeWare tools; and we ran an extremely successful sprint. At the peak, we had over 30 people sprinting on BeeWare projects; and we handed out over 20 challenge coins to first time contributors. Many of the new features in this status update can be attributed to contributions from sprint participants.
We modified Toga's Window API to allow setting the content of the window when the window is constructed, and improved the APIs for replacing children in an existing window layout.
We modified how validation of TextInput widgets are handled so that change handlers aren't invoked until validation has been performed.
We modified how the DetailedList is created on Android so that the dependency on the native SwipeRefreshLayout widget only exists if your app actually uses a DetailedList widget.
We improved the error handling around camera permissions on macOS, and ensured that Briefcase will generate the right permissions for macOS Sonoma.
We diagnosed some issues associated with code signing on macOS when running on iCloud-mirrored drives, and when Git has been configured to preserve Windows newlines. We also improved the error handling when notarisation fails.
We formally documented the plugin extension points that Briefcase provides. With this formally documented interface, Pygame-CE and PPB, have taken formal ownership of their Briefcase bootstraps.
We formally adopted PEP 621 format for specifying license files in Briefcase.
We loosened the restrictions on bundle identifiers, and improved handling of applications with special characters in their formal names.
We developed a draft implementation of a change that will allow Briefcase to package console applications. We expect this change will land in the next week or so, and be released soon after that.
We started work on removing binary stubs from the macOS and Windows app templates. This was starting to become a significant performance issue for first-time Briefcase users.
We improved the mechanism for invoking methods in Rubicon ObjC, making it possible to invoke methods with repeated argument names.

What's next?

In June, we're expecting to see progress in three main areas.

Firstly, we'll be finalising the work on packaging console applications. We expect to see a Briefcase release by mid month that will incorporate this, and all the other improvements that have landed over the last month.

Secondly, we'll be working on the APIs for the Toga App and Window classes. We've already done a lot of prototyping work in this area; once this work is complete, Toga should have support for apps without a menubar in their main window, support for status bar apps without a main window, vastly improved abilities to customise standard menu items, and a stable API for document-based apps.

Thirdly, we'll start looking at the broader CPython binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take much longer than a month to complete, but we hope to be able to share some progress in June.

Want to get involved?

Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:

Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.

What we've done

iOS is officially a Tier 3 supported platform for CPython! All the patches needed to support iOS have been merged, and a buildbot has been deployed to verify that CPython can run on iOS. As a result, PEP 730 has been moved into "Final" status.
Android support in CPython is getting very close to completion. The last three patches (adding a test harness for running the test suite on Android, redirecting stdout and stderr to the Android log, and updating sysconfig to support Android) are currently in review; once those have been merged, and a buildbot has been deployed, Android should also be at Tier 3 status.
We landed a new Geolocation service for Toga, providing access to GPS data on mobile devices and macOS.
We made some modifications to how Toga handles application icons, removing the need to duplicate the icon in application data. These changes are in final review.
We added a new wizard to add a Briefcase configuration to an existing Python project.
We modified how Briefcase handles splash screens on mobile devices, and corrected some issues with icons seen on recent Android releases.
We corrected a problem in Rubicon ObjC caused by a change to the ctypes module in CPython 3.13. It might be possible to upstream this fix to CPython itself; but for now, Rubicon ObjC is able to support Python 3.13.0a6.
We drafted a new tutorial step about customising application appearance. This update is in review, and should be live in the near future.

What's next?

The bulk of May will be taken up by preparing for and attending PyCon US. We're presenting a talk and a tutorial; we're also presenting at the Language Summit, we will have a booth in the community section of the Expo Hall, and we'll be there for the first 3 days of the sprints. If you're coming to Pittsburgh and you'd like to attend that tutorial session, ticket sales are open!. We're also hoping that we'll be able to wrap up the work on Android support in CPython, and start work on supporting command line applications in Briefcase.

Want to get involved?

Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:

Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.

The Buzz

What we've done

What's next?

Want to get involved?

What we've done

What's next?

Want to get involved?

Q3 progress

Q4 priorities

Longer term goals

What we've done

What's next?

Want to get involved?

What we've done

What's next?

Want to get involved?

What we've done

What's next?

Want to get involved?

Q2 progress

Q3 priorities

Longer term goals

Summary

What we've done

What's next?

Want to get involved?

What we've done

What's next?

Want to get involved?

What we've done

What's next?

Want to get involved?

Archive