Test log
Softgen test data
Raw results for the Softgen review. The verdict is in the review.
- Tested
- 27 October 2026
- Tester
- Miles Foster
- Account
- Bought for this review at the public price
- Tests
- 10
- Screenshots
- 12
- Method
- Published methodology
- Environment
- Google Chrome on desktop
Results
| ID | Test | Key measurement | Score |
|---|---|---|---|
| T01 | Prompt to Working App | Brief to a built app: About 11 min | n/a |
| T02 | Database & Admin | – | n/a |
| T03 | Payments & Email Actions | – | n/a |
| T04 | Iteration & Credit Burn | Changes run: 1 of 12 | n/a |
| T05 | Publish, Speed & Mobile | A live app on the trial: Not possible | n/a |
| T06 | Support & Cancellation | – | n/a |
| T07 | Spec Accuracy | Checks passed: 15 of 22 run | 3/5 |
| T08 | Sign-in & Access Control | Attacks that succeeded: 2 of 2 | 2/5 |
| T09 | Code Export & Ownership | Code visible on the trial: No | 1/5 |
| T10 | Pricing & Cost to Finish | Paid: $0 | 3/5 |
| Overall (in the review) | 2.3/5 | ||
Prompt to Working App
n/aNot Tested- Method
- The Fitting Room brief was pasted word for word into the prompt box on Softgen's dashboard at about 21:48 UTC on 27 October 2026, in the Default mode.
- Brief to a built app
- About 11 min
- Requests
- 2
- Credits used
- 66 of 75
- Remark
- The test ends at a live app with 25 of the 30 checks passing. No live app can exist on the free trial, so build speed is not graded. The time to a built app is reported as a fact.
Raw notes
The Fitting Room brief was pasted word for word into the prompt box on Softgen's dashboard at about 21:48 UTC on 27 October 2026, in the Default mode.
Softgen asked no questions about the brief. It planned the app and then stopped, asking me to click Enable Supabase, which needs a paid plan. I told it to carry on without a database and keep the data in the browser. It then built the app in about nine minutes, so the first working draft came about eleven minutes after the brief. It used 66 credits in all.
- The app ran only in the builder preview, and it needed a request that was not in the brief.
Database & Admin
n/aNot Tested- Method
- I created records through the app, reloaded the preview and used the admin screens.
- Remark
- The six data checks need a database, so there is no grade.
Raw notes
I created records through the app, reloaded the preview and used the admin screens.
The free trial cannot use Managed Supabase: the Connect Now button is greyed out with the words Subscribe to use Managed Supabase, or connect your own Supabase below. I did not connect my own account. The app therefore keeps its records in the browser, where they survived a reload. A booking, an order or a message made in one browser is invisible in any other, so an admin on another device would never see a visitor's Ask the studio message. Redeploy and the data panel could not be tried.
- Redeploy, a design change over data and the export of records were not tried.
Payments & Email Actions
n/aNot Tested- Method
- Payments and emails need keys that are the owner's, so the six checks C24 to C29 are left out.
- Remark
- Not graded, as the methodology allows when the keys are not supplied.
Raw notes
Payments and emails need keys that are the owner's, so the six checks C24 to C29 are left out.
The pass page carries a note that it is a simulated payment, and its button added five credits and an order record to the browser's storage without any Stripe checkout. No email was sent. I created no Stripe account and entered no card.
- No real payment or email was made.
Iteration & Credit Burn
n/aNot Tested- Method
- One of the twelve changes was run as a chat request: E04, the About page.
- Changes run
- 1 of 12
- Worked first time
- 1
- Credits for the About page
- 9
- Remark
- Fewer than 3 of the 12 changes ran, so there is no grade.
Raw notes
One of the twelve changes was run as a chat request: E04, the About page. Then I asked for E05, the capacity change, with no credits left.
E04 worked first time and passed: the About page has the address, phone and email, the owner's name and both prices, and it is linked in the menu. It used the last 9 credits. The E05 request was refused with Not enough credits to continue, and a window offered a one-time pack of 200 credits for $5 or Starter at $25 a month. I clicked neither. Softgen also suggested three extras I had not asked for: testimonials, a map and an FAQ.
- A chat edit to an app in the builder, not to a live app.
Publish, Speed & Mobile
n/aNot Tested- Method
- I opened the Publish screen in the project settings on the free trial.
- A live app on the trial
- Not possible
- Plan that publishes
- $25 a month
- Remark
- There is no app to publish, so there is no grade.
Raw notes
I opened the Publish screen in the project settings on the free trial.
Publish says Get Starter to publish, with the line Deploy your project to the web. The credit window repeats that publishing, GitHub export and custom domains require a subscription. No public address exists, so no speed test, layout check or uptime monitor could run. The builder's preview address opened in a browser, but it is a sandbox that the builder starts and stops, not a published app.
- I did not try the paid plan and nothing was uploaded anywhere.
Support & Cancellation
n/aNot Tested- Method
- I emailed three questions to support@softgen.ai on 27 October 2026: how to stop people signing up as admin, how to export data and code, and how to cancel a paid plan.
- Remark
- Not graded until a reply arrives.
Raw notes
I emailed three questions to support@softgen.ai on 27 October 2026: how to stop people signing up as admin, how to export data and code, and how to cancel a paid plan.
No reply had arrived when I wrote this. I paid nothing, so there was nothing to cancel, and the account pages showed no cancel control, as expected on a free account.
- The cancel path of a paid plan was not tested.
Spec Accuracy
3/5Limited- Method
- The 30 checks were run by hand on the app in the builder preview, not on a live app.
- Checks passed
- 15 of 22 run
- Checks not run
- 8
- Seed facts on screen
- 10 of 10
- Remark
- Fifteen of the 22 checks that ran is 68 percent, which is a 3 on the proportional scale. It is provisional, because eight checks could not run and none ran on a live app.
Raw notes
The 30 checks were run by hand on the app in the builder preview, not on a live app. Six payment and email checks (C24 to C29) are left out, because Softgen's Stripe button is a simulation and no email can be sent without keys that are not mine. Two more could not run: C10, the full-class rule, needs eight members, and C17, saving an edit to a class, was not completed. Twenty-two ran.
Fifteen passed: sign-up lands logged in, log-out and log-in, the timetable with the three classes, their times, instructors and places, booking, the booking on My bookings, cancelling and getting the place back, one member never seeing another's bookings, the admin adding and deleting a class, the admin seeing every booking, the CSV export, the count of bookings per class, and the Ask the studio form with the admin seeing the message. Seven failed: the password reset, the instructor screens (My classes sends the instructor back to the home page, so C04, C13, C14 and C15 fail), the message to a member with no credits (nothing appeared), and the rule to invent nothing, because Softgen added class descriptions, a Save $25 line and two instructor accounts that the brief never asked for. All ten seed facts are on screen once the About page is added, the studio owner's name included.
- The grade describes the app in the builder preview, with data kept in the browser, on the free trial.
Sign-in & Access Control
2/5Limited- Method
- I signed up as a member, a second member and an admin, logged in as the seeded instructor, tried the password reset, and ran the two attacks from the brief against the app in the builder preview.
- Attacks that succeeded
- 2 of 2
- Passwords stored in plain text
- Yes
- Remark
- Both attacks succeed and the roles are only labels: 2.
Raw notes
I signed up as a member, a second member and an admin, logged in as the seeded instructor, tried the password reset, and ran the two attacks from the brief against the app in the builder preview.
Sign-up and log-in work for members and the admin. The sign-up form lets anyone tick Admin, and the account then opens the admin screens with every booking, every message and the class editor, so attack two, calling an admin action as a member, succeeds without any trick. Attack one, reading another member's bookings, also succeeds: the app keeps all users, bookings and orders in the browser's storage, and member B read member A's booking there, together with every account's password in plain text. The password reset asks only for an email address and then offers a new-password box, with no email and no check. The instructor screens never open. Softgen's own security scan was not run.
- The cause is the free trial having no database, because the app keeps its data in the browser. With Managed Supabase on a paid plan, the result may differ and was not tested.
Code Export & Ownership
1/5Limited- Method
- I opened the Code Editor and the GitHub screens on the free trial.
- Code visible on the trial
- No
- Export found
- No
- Remark
- I found no way to take the app out on the trial: 1. It is provisional, because the paid export was not tried and support has not answered.
Raw notes
I opened the Code Editor and the GitHub screens on the free trial.
The Code Editor says Get Starter to use Code Editor, with the words Edit and copy project code. The GitHub screen says Get Starter to connect GitHub. Softgen's dashboard had listed GitHub export under what the free trial includes, and the credit window says it needs a subscription. I found no download of the code or the data on the trial. Starter lists GitHub export. I did not run any code elsewhere and did not read the terms.
- The grade describes the free trial. Starter's GitHub export was not tested.
Pricing & Cost to Finish
3/5Limited- Method
- The pricing page, the wallet, the credit window and the plan limits were read on 27 and 28 October 2026.
- Paid
- $0
- Credits used
- 75 of 75
- Remark
- The price is clear and nothing billed, but the trial ended after two requests and the dashboard promised a database and an export that the trial does not give: 3. It is provisional, because no paid plan was tried.
Raw notes
The pricing page, the wallet, the credit window and the plan limits were read on 27 and 28 October 2026.
The free trial is $0 with 75 credits once and one project. The first request, with the build, used 66 credits and the About page used 9, so two requests used everything, and a full test of twelve changes would need many more. The paid plans are $25 a month for 500 credits, 10 projects, GitHub export and Basic Supabase, and $49 a month for 1,500 credits, more models, custom domains and backups. A one-time pack of 200 credits costs $5, once per account. Credits stop at zero and I saw no overage or auto top-up. The running cost of a live app is unknown.
- A live app's running cost is not known.
Coverage
Tested
- One brief typed word for word, with the builder's own request to enable a database answered from the brief's needs
- The app in the builder preview: sign-up as member, instructor and admin, timetable, booking, cancelling, class credits, My bookings, the admin screens, the CSV export and the Ask the studio form
- One change by chat (the About page) and a second request that the credit wall refused
- The Supabase connection, Publish, GitHub and Code Editor screens
- The wallet, the credit meter and the pricing page
- One support email with three questions
Not tested or limited
- Tested on the free trial only: publishing, Managed Supabase, the code editor, GitHub export and the paid credit allowances were not tried
- No live app exists, so there is no test app, no uptime record and no speed test
- The app runs without a database, because the free trial cannot use Managed Supabase and I did not connect my own Supabase account. Its data lives in the browser
- The Stripe button in the app is a simulation, so payments and emails are left out
- The free credits ran out after two requests, so eleven of the twelve changes were not run
- Two checks could not run: the full-class rule, which needs eight members, and saving an edit to a class
- Support is not graded: the email was sent on 27 October 2026 and no reply had arrived when I wrote this
- I did not read the terms and did not read what other users say
Still to test
- Publishing on Starter, a public address, speed and uptime
- Managed Supabase: sign-in, the database and the two access attacks
- The remaining eleven changes
- GitHub export, run elsewhere
- A reply from support and cancelling a paid plan