The current SpikerSoft registration flow requires users to be at least 16 years old and provide a valid email address. This design prevents younger users (under 16) from creating their own accounts directly. Instead, a parent must first create a Parent Account and then add a Child Account through the parental control panel. However, this process lacks visual feedback and intuitive guidance, making it confusing for both parents and younger users.
Issue Description
The registration system enforces age and email validation correctly but does not provide clear instructions or visual cues for users under 16. Parents and children are unaware of the correct flow for account creation, leading to frustration and failed registration attempts. The absence of tutorials or contextual guidance reduces accessibility and usability for families.
Environment
Property
Value
Application
SpikerSoft
Module
Registration / Account Creation
Environment
Production
Browser
Firefox / Chrome
Operating System
Windows 11
Version
v2026.10.04d
Device
Desktop
Preconditions
User attempts to create an account with a birth date indicating age under 16.
Steps to Reproduce
Navigate to the Create Account page.
Enter a birth date indicating age under 16.
Attempt to proceed through the registration flow.
Observe that the system blocks account creation and provides no clear guidance for parental setup.
Expected Result
The system should provide clear visual feedback explaining that users under 16 must have a parent create their account.
A guided flow should direct parents to the parental control panel to add a child account.
Tutorials or tooltips should explain the process for both parent and child users.
Actual Result
Registration fails for users under 16 without clear explanation or guidance.
Parents and children are unaware of the correct procedure.
No visual or interactive feedback is provided.
Evidence
Screenshot shows the registration form with age restriction and missing email validation feedback.
Impact
Reduces accessibility for younger users.
Causes confusion during account creation.
Limits user engagement and onboarding efficiency.
Frequency
Always
Reproducibility
100%
Severity
Medium (UX enhancement)
Suggested Improvement
Implement a dynamic registration flow that detects under-16 users and redirects them to a parental setup guide.
Add visual feedback and contextual tooltips explaining the process.
Include tutorials or onboarding steps for parents and children.
During product marketing, provide clear guides and visual examples to make the registration process intuitive and accessible.
## Summary
The current **SpikerSoft registration flow** requires users to be at least **16 years old** and provide a valid email address. This design prevents younger users (under 16) from creating their own accounts directly. Instead, a parent must first create a **Parent Account** and then add a **Child Account** through the parental control panel. However, this process lacks visual feedback and intuitive guidance, making it confusing for both parents and younger users.
## Issue Description
The registration system enforces age and email validation correctly but does not provide clear instructions or visual cues for users under 16. Parents and children are unaware of the correct flow for account creation, leading to frustration and failed registration attempts. The absence of tutorials or contextual guidance reduces accessibility and usability for families.
## Environment
| Property | Value |
|-----------|--------|
| Application | SpikerSoft |
| Module | Registration / Account Creation |
| Environment | Production |
| Browser | Firefox / Chrome |
| Operating System | Windows 11 |
| Version | v2026.10.04d |
| Device | Desktop |
## Preconditions
User attempts to create an account with a birth date indicating age under 16.
## Steps to Reproduce
1. Navigate to the **Create Account** page.
2. Enter a birth date indicating age under 16.
3. Attempt to proceed through the registration flow.
4. Observe that the system blocks account creation and provides no clear guidance for parental setup.
## Expected Result
- The system should provide **clear visual feedback** explaining that users under 16 must have a parent create their account.
- A **guided flow** should direct parents to the parental control panel to add a child account.
- Tutorials or tooltips should explain the process for both parent and child users.
## Actual Result
- Registration fails for users under 16 without clear explanation or guidance.
- Parents and children are unaware of the correct procedure.
- No visual or interactive feedback is provided.
## Evidence
- Screenshot shows the registration form with age restriction and missing email validation feedback.
## Impact
- Reduces accessibility for younger users.
- Causes confusion during account creation.
- Limits user engagement and onboarding efficiency.
## Frequency
Always
## Reproducibility
100%
## Severity
Medium (UX enhancement)
## Suggested Improvement
- Implement a **dynamic registration flow** that detects under-16 users and redirects them to a **parental setup guide**.
- Add **visual feedback** and contextual tooltips explaining the process.
- Include **tutorials or onboarding steps** for parents and children.
- During product marketing, provide **clear guides and visual examples** to make the registration process intuitive and accessible.
Tracker sweep 2026-10-06. The report is valid, but closing as superseded by spikerj/spikersoft-angular#1447, which already plans exactly this fix.
Confirmed on angular master. The cut-off is 18, not 16: basic-info-step.ts:277 sets isUnder18 when age < 18, and the backend InitiatePreRegistrationCommandHandler.cs:30 rejects age < 18 too. An under-18 birthday gets one red banner, "You must be at least 18 years old to register" (registration.basicInfo.ageGateError). The form stops there, with no next step and no guidance for parents. That's the dead end this report describes.
Where the fix is tracked. This tracker (spikersoft-issues) is retired. The fix belongs to the approved Join SpikerSoft sign-up redesign, issue spikerj/spikersoft-angular#1447, which specifies an under-18 panel in place of this banner:
"Accounts for under-18s are set up by a parent", with the Parent Dashboard → Add child account steps;
I'm a parent → sign in and go to the Parent Dashboard;
Copy link for my parent / share, Explore without an account, Wrong date;
nothing is stored or sent for the under-18 visitor.
The design brief, spikerj/spikersoft-angular#1442, has the matching frames ("Under-18 panel: default, link copied, share sheet"). Further detail belongs on #1447.
**Tracker sweep 2026-10-06. The report is valid, but closing as superseded by spikerj/spikersoft-angular#1447, which already plans exactly this fix.**
**Confirmed on angular `master`.** The cut-off is **18**, not 16: `basic-info-step.ts:277` sets `isUnder18` when `age < 18`, and the backend `InitiatePreRegistrationCommandHandler.cs:30` rejects `age < 18` too. An under-18 birthday gets one red banner, "You must be at least 18 years old to register" (`registration.basicInfo.ageGateError`). The form stops there, with no next step and no guidance for parents. That's the dead end this report describes.
**Where the fix is tracked.** This tracker (`spikersoft-issues`) is retired. The fix belongs to the approved Join SpikerSoft sign-up redesign, issue spikerj/spikersoft-angular#1447, which specifies an **under-18 panel** in place of this banner:
- "Accounts for under-18s are set up by a parent", with the Parent Dashboard → **Add child account** steps;
- **I'm a parent** → sign in and go to the Parent Dashboard;
- **Copy link for my parent** / share, **Explore without an account**, **Wrong date**;
- nothing is stored or sent for the under-18 visitor.
The design brief, spikerj/spikersoft-angular#1442, has the matching frames ("Under-18 panel: default, link copied, share sheet"). Further detail belongs on #1447.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
The current SpikerSoft registration flow requires users to be at least 16 years old and provide a valid email address. This design prevents younger users (under 16) from creating their own accounts directly. Instead, a parent must first create a Parent Account and then add a Child Account through the parental control panel. However, this process lacks visual feedback and intuitive guidance, making it confusing for both parents and younger users.
Issue Description
The registration system enforces age and email validation correctly but does not provide clear instructions or visual cues for users under 16. Parents and children are unaware of the correct flow for account creation, leading to frustration and failed registration attempts. The absence of tutorials or contextual guidance reduces accessibility and usability for families.
Environment
Preconditions
User attempts to create an account with a birth date indicating age under 16.
Steps to Reproduce
Expected Result
Actual Result
Evidence
Impact
Frequency
Always
Reproducibility
100%
Severity
Medium (UX enhancement)
Suggested Improvement
Tracker sweep 2026-10-06. The report is valid, but closing as superseded by spikerj/spikersoft-angular#1447, which already plans exactly this fix.
Confirmed on angular
master. The cut-off is 18, not 16:basic-info-step.ts:277setsisUnder18whenage < 18, and the backendInitiatePreRegistrationCommandHandler.cs:30rejectsage < 18too. An under-18 birthday gets one red banner, "You must be at least 18 years old to register" (registration.basicInfo.ageGateError). The form stops there, with no next step and no guidance for parents. That's the dead end this report describes.Where the fix is tracked. This tracker (
spikersoft-issues) is retired. The fix belongs to the approved Join SpikerSoft sign-up redesign, issue spikerj/spikersoft-angular#1447, which specifies an under-18 panel in place of this banner:The design brief, spikerj/spikersoft-angular#1442, has the matching frames ("Under-18 panel: default, link copied, share sheet"). Further detail belongs on #1447.