Newtown User Manual

Welcome to Newtown, your group computer! It’s more than a tool - it’s a shared space where your group can build, use, and evolve all the apps you need together. You don’t need to be a systems architect or a programmer. All you need is an idea. Describe what you want in simple english, and the system takes care of everything else.

Are you a developer? Check out the Developer Manual for technical details and API references.

How it works ?

  1. Say what you want to build: Just describe your idea in plain words.

  2. Anyone can add or improve things: Everyone in the group can create and shape the apps.

  3. Safe to try things: You won’t break what others built, and you can still use / extend it.

  4. Preview everything: See your changes live, from whole app to individual parts before publishing.

  5. Newtown helps to build and run: Everything technical is handled for you.

Getting Started

Start by describing the first thing your group wants to build. Think about a simple activity your group wants to coordinate - like organizing an event, tracking shared tasks, managing sign-ups, or keeping a list of resources.

Write a prompt that explains the goal and how people in the group should use it. For example, you might want a way for members to share updates, details needed to sign up, or describe who should be able to see / update different parts of the app.

Example Prompts

Create a task tracker where team members can assign duties, set deadlines, and see who is responsible for each task. Make sure everyone can view tasks, but only assigned members can mark them complete.
Build a potluck signup where members can add the dish they’re bringing, see who else is participating, and update their own entries without affecting others’ choices.
Make a shared inventory list for our shop so people can track items, quantities, and who last updated them. Allow everyone to view the inventory, but only designated staff can modify quantities or add new items.

Many apps begin by supporting basic group activities like knowing who’s part of the group, sending messages, sharing updates, or helping members exchange things. Defining these core functions upfront helps you create powerful combinations later.

How to Prompt

Here’s a guide on how to effectively communicate your ideas to Newtown, from your very first app to advanced features.

Add / Update Features

Describe the changes you want to make clearly. You can add new features, improve existing ones, or modify how parts of the app work. Be specific to reduce number of turns.

Example Prompts

Add a feature that lets team members mark tasks as complete and automatically notify the assigned person.
Modify the signup form so members can also leave notes about what they are bringing.
Improve the inventory list so it highlights items that are running low and only managers can update quantities.

Foundational blocks

Think about the basic activities that keep your group coordinated. Focus on core functions like knowing who’s in the group, sharing updates or messages, and helping members exchange things or coordinate work. Add these blocks early on to aid powerful combinations later.

Example Prompts

Add a messaging feature so members can post updates visible to the whole group.
Set up a member directory so everyone can see who is part of the team.
Create a simple peer-to-peer exchange where members can offer and request resources.

Combine foundational blocks

Start a new app by combining basic group functions you’ve used before, like member management, messaging, task tracking, or resource sharing. Think about how these functions can work together to support a complete workflow for your group.

Example Prompts

Build an event planner app where members can RSVP, post messages, and track who is bringing what.
Create a team coordination app that combines a task tracker with a messaging board for updates.
Make a shared project hub where members can see tasks, share files, and communicate progress.

Coordination / Side Effects

Use prompts to describe how actions in one part of your app should affect other apps. Explain in plain language what should happen when something changes.

Example Prompts

When a member signs up for a task, automatically update the task list for everyone involved.
Completing a volunteer shift should adjust the schedule and notify the team responsible.
Adding a new item to the inventory should update stock counts and alert the staff managing supplies.

Update Styles & Layouts

Use prompts to adjust how your app looks and feels. You can change layouts, colors, styles, or the arrangement of sections to make the app easier and more enjoyable for your group to use. Be clear about which parts you want to update.

Example Prompts

Change the dashboard layout so tasks are grouped by priority and displayed in cards.
Update the color scheme to make high-priority items stand out and headings easier to read.
Reorganize the signup form so fields are grouped logically and labels are clearer.

Fix Things

Use very specific prompts to describe exactly what isn’t working or needs correcting. Include details about the part of the app, what went wrong, and what you want to happen instead. The clearer you are, the faster the system can fix it.

Example Prompts

The task completion checkbox isn’t saving. Make sure checking a task marks it complete and updates the assigned member’s list.
The RSVP form doesn’t show who has signed up. Fix it so all members can see the list of participants for each event.
Inventory quantities aren’t updating when a staff member adds an item. Correct it so the count increases immediately and shows to all staff.

Test Data

Start by adding some example entries for the things your app manages. This helps your group see how the app works with real information. Focus on adding a few items for each type of thing, so people can interact and test the app.

Example Prompts

Add sample tasks with names, due dates, and assigned team members so we can test the task tracker.
Create a few example events with titles, dates, and locations for the event planner app.
Add some items to the inventory with names, quantities, and owners so staff can start managing stock.

Preview & Publish

  • Preview: Use the preview to see all changes in real time before they go live. The preview environment is shared, so everyone in the group sees updates instantly.
  • Publish: When you’re ready, publish your changes to make them live for all users. Choose a good time to publish so your group can see a stable version of the app.

App Organization

A group can build and run multiple apps in Newtown. Each app is organized into blocks and pages.

Blocks

Blocks are the core functional units of an app. Each block represents a capability such as identity, messaging, tasks, or auctions. Blocks keep related logic and data together so they remain modular and reusable.

A block typically contains:

  • Fields – The pieces of data stored for an item (for example: status, title, due date).
  • Actions – Operations that change data (create, update, delete, or custom behaviors).
  • Components – UI triggers that initiate actions (such as buttons or controls).

Blocks operate independently, which keeps functionality clean and maintainable.

Coordination

Coordination handles side effects between blocks. When something changes in one block, coordination defines what should happen in others. This keeps blocks independent while still allowing apps to respond to events.

Pages

Pages bring blocks together into a usable interface. A page organizes forms, lists, and views so members of the group can interact with the app.

While blocks define how things work, pages define how people use them.

Looking for code examples? The Developer Manual covers the framework APIs.