Skip login if you don't need it

A common request is to build login or authentication into prototypes. Before adding auth, consider:

Do you actually need it? Published Spaceship prototypes are already restricted to public officers with .gov.sg email addresses—members of the public cannot access them. This built-in access control may be sufficient for your prototyping needs.

It complicates testing. Adding authentication means you'll need to log in repeatedly after each iteration, slowing down your testing cycle.

Keep it simple for validation. The goal of a prototype is to validate your idea quickly. Authentication adds complexity that can distract from testing core functionality.

If your prototype genuinely requires user-specific data or role-based access, go ahead and include it. But if you're adding login "just in case"—skip it and move faster.