Chris | 4 November 2025

Thanks to Wycliffe UK for funding the development of Scriptoria 2. It requires AppBuilders 13.2 due to improvements in security. I will be writing additional posts with more details on the individual changes. The new version was developed to provide these important improvements:

  • improve the performance (no wait animation when viewing a project or product files!)
  • improve the onboarding process for organizations and users
  • improve the workflow system used to handle changes in the publishing process

We built Scriptoria 2 with the same technology used for the Scripture PWA (using Svelte/SvelteKit), which will simplify the support/maintenance of the website. Some additional unplanned improvements came during the development:

  • respond to the light/dark mode of the operating system
  • improved layout on mobile devices
  • “upload & rebuild” button available in AppBuilder 13.2 when the project has products that are in a completed state
  • show Author option in all workflows only if Authors are defined
  • return to the project or tasks when the workflow goes to the next step that doesn’t require the user
  • show breadcrumb in the workflow to easily return to the project
  • correct pagination of projects
  • improved search
    • search users by email
    • search projects by package name
  • improved updating of the user’s browser when changes happen on the server
  • display AppBuilder version of products (even previously built products)
  • cleaner display of a project in the project list
  • browsing to a project using the URL (e.g. in a new browser tab or clicking a link in an email) will switch the current organization (and not fail to load!)

It will be easier to implement new features as well. Here are a few that are in the works:

  • Rebuild all products that are older than the current AppBuilders version (Organization Admin will be able to do this for their organization, or the Scriptoria Admin can do this for the whole site). The project will need to opt in for this with a new project setting.
  • Publish on rebuild (without having to do the “Verify and Publish” step in the workflow). The project will need to opt in for this with a new project setting.
  • When adding an existing app to Scriptoria, download and use the existing Google Play Listing that was uploaded manually. The user will be instructed to add a Publishing Property during the workflow and import the Google Play Listing information from a product file (play-listing.zip) created during the build process. AppBuilders will be changed to allow importing from this product file.
  • Detect that the project is being published to Google Play and uses the Accounts feature and provide a Data Deletion URL in the data-safety.csv that is specific to the store and project (we will make sure it is acceptable to Google Play). Requests from users will be emailed to the project owner and organization administrators. We are looking to add a workflow task to aid in tracking and handling the request.

We are so excited to deploy Scriptoria 2. Please contact me if you see an issue or have questions.

For His Great Name,

Chris Hubbard