List view
- No due date•25/25 issues closed
**User Story**: Developers have an intuitive and simplified experience on PWABuilder.com when testing and packaging their apps **Owner**: @joshsach Developers find the current linear website flow confusing, and sometimes get stuck between the base package state and store packaging state. We plan to redesign the flow to make it as easy as possible to go from entering a url to packaging a website, while maintaining the ability to generate and edit manifest or generating a service worker. As part of this redesign: * We will simplify the scoring system for PWAs * Introduce an always visible packaging and retest buttons * Introduce a smart ToDo checklist * Componentize Manifest and Service Worker generation tools * Remove the badging and achievements from this first re-design
No due date•35/36 issues closed**User Story**: Our engineering architecture removes friction and allows us to easily innovate and scale while enabling the community to participate **Owner**: @nmetulev, @amrutha95 Our engineering services and processes should be setup to enable anyone to quickly understand how our products are built, how to get started adding code, where and how to fix issues, how to reuse code, and how to add and deploy features with minimal overhead. To do this, we need to: * Enable sharing code across PWA Builder suite of products by moving various repos to one main mono-repo * Document the code structure and how all products are connected * Document the architecture of all services and simplify where possible * Define best practices, naming conventions, and engineering processes * Build best in class contributing guidelines * Automate everything
No due date•38/38 issues closed**User Story**: PWA Product suite has an informative and intuitive documentation ecosystem **Owner**: @zateutsch **Deliverable goal**: Create a documentation resource that covers all of the PWA Builder toolchain and serves as a catch-all for building great PWAs. A repository specific to documentation will be added soon, and current pwa-builder docs wikis will be migrated to contribution guidelines. All documentation for the PWA Builder tool chain will live in a single docs resource.
No due date•46/48 issues closed**User Story**: Developers have the best manifest creation and validation tools for building great PWAs **Owner**: @jgw96, @Jaylyn-Barbee PWABuilder has several opportunities to improve the developer experience to ensure developers are successful in their journey of creating and publishing PWA. * Minimize the number of issues users run into when packaging PWAs. Today we get dozens of issues a week from users who are unable to package their apps because of issue with their manifest. These issues require someone from our team to look at their manifest, where the majority of issues are an obvious typo or type mismatch in their manifest. * Share the same editing and creation experience across all PWA Builder tools. Today, PWABuilder.com and PWA Studio have separate implementations of manifest editing and validation tools. Those tools should be factored out into a shared library, allowing us to reuse code and build additional tools faster * Educate developers on best practices, new features, and upcoming standards directly in the dev tools by keeping strict type validation, clear error messages with plan of action, and links to rich documentation. This will help developers add features to their manifest they might not have before, and feel confident about building a manifest that will work when they are packaging their PWAs
No due date•49/49 issues closed**User Story**: Developers are able to sign in save their progress/state on PWABuilder.com **Owner**: @joshsach
Overdue by 3 year(s)•Due by June 30, 2022•26/26 issues closed