RankDude

Test log

Softr test data

Raw results for the Softr review. The verdict is in the review.

Tested
26 October 2026
Tester
Miles Foster
Account
Free demo account, signed up by RankDude, nothing paid to the brand
Tests
8
Screenshots
8
Environment
Google Chrome on desktop

Results

IDTestKey measurementScore
T01Prompt to Working AppBrief to a built app: about 25 min1/5
T02Spec AccuracyChecks passed, of 24 without keys: 82/5
T03Sign-in & Access ControlAttacks blocked: 2 of 24/5
T04Database & AdminChecks proved: 5 of 64/5
T05Iteration & Credit BurnChanges that worked: 5 of 122/5
T06Publish, Speed & MobileTime to publish: 5 s3/5
T07Export & OwnershipCode export found: none1/5
T08Pricing & Cost to FinishPaid: $03/5
Overall (in the review)2.5/5
T01

Prompt to Working App

1/5Tested
Method
The Fitting Room brief was pasted word for word (1,689 characters) at 01:07 UTC on 26 October 2026.
Brief to a built app
about 25 min
After Create my app
about 3 min
Follow-up prompts
13
Checks passing, of 20 needed
8
Remark
The scale stops when 20 of the 24 checks pass. Only 8 ever did: 1, longer, or never reached.

Softr: the build wizard asking how users will log in, with Email, Google and SSO options and three steps along the top.

Softr: the build wizard asking how users will log in, with Email, Google and SSO options and three steps along the top.
T01-1 One of the wizard's questions before the build.
Raw notes

The Fitting Room brief was pasted word for word (1,689 characters) at 01:07 UTC on 26 October 2026. The clock stops when the app is live and the checks pass: 25 of 30 on the full scale, applied here as 20 of the 24 checks that need no keys of mine.

Softr turned the brief into a wizard. I answered from the brief only: bookings by the member in the app, no approval, log-in by email, anyone can sign up, and Softr's own navigation (the brief is silent on it). That took about five minutes of answering. My first click on Create my app did not start the build because a theme had to be picked.

After I picked the first theme and clicked again, the app was ready about three minutes later (01:32 UTC), 25 minutes after the brief was submitted. It was published at 01:43 UTC with the invented data still in it.

Then came 13 follow-up prompts, a few of them sent twice after a timeout, and hand edits in the Data view. After the last one only 8 of the 24 checks passed, so the 20 the scale asks for were never reached.

  • The time to a first draft is good, but the grade follows the finish line.
T02

Spec Accuracy

2/5Tested
Method
The checks were run against the live app, by hand, with a note per check.
Checks passed, of 24 without keys
8
Left out, need the owner's keys
6
Invented bookings
32
Invented users
10
Remark
8 of 24 is 33%, which is the 2 band. One fewer pass would have been a 1.

Softr editor after the first build, with the chat summary on the left and the Fitting Room home page on the right listing Sunrise Yoga, HIIT Cardio Blast and other classes I never asked for.

Softr editor after the first build, with the chat summary on the left and the Fitting Room home page on the right listing Sunrise Yoga, HIIT Cardio Blast and other classes I never asked for.
T02-1 Softr's editor right after the build: the invented classes.

Softr test app admin page: the Classes table and the Bookings table, where the Class Name, Class Day and Class Start Time columns are empty for every booking, with a message that the data was exported.

Softr test app admin page: the Classes table and the Bookings table, where the Class Name, Class Day and Class Start Time columns are empty for every booking, with a message that the data was exported.
T02-2 The admin's bookings table: the class columns are blank.
Raw notes

The checks were run against the live app, by hand, with a note per check. The six checks that need your own Stripe and email keys (C24 to C29) are left out, so the thresholds are applied to the 24 that remain: 4 needs 80% or more (20 or more), 3 needs 60% (15), 2 needs 33% (8) and 1 is below that.

8 of 24 checks passed, which is 33%. Passing: sign-up by emailed code (C01), log-out and log-in (C02), the emailed code in place of a password reset (C03), the admin's Add class form, which added a class that the member timetable then showed (C16), the Edit class menu item (C17), delete, after which the member's class count went back to 3 (C18), the admin seeing all 32 bookings (C19) and the Ask the studio form writing a record (C22).

The other 16 failed. Members have no Book button and no My Bookings page (C07 to C12). No coach screen could be reached (C04, C13 to C15), because a new sign-up gets no user group and the roles exist only on the invented sample users. The CSV export downloads, but its class columns are blank (C20), and the per-class count is a heading with one total (C21). The timetable shows wrong times (C05) and no places left (C06). I could not confirm that the admin sees the Ask the studio submissions as a list (C23).

The brief says "use only these facts". Softr invented them anyway (C30). The first version listed eight classes, such as Sunrise Yoga and HIIT Cardio Blast, with prices from $20 to $35, 32 bookings, 8 studio inquiries and 10 sample users with example.com addresses in Admin, Instructor and Member groups. None of my three classes was there. Softr told me it cannot delete records, so I deleted the invented classes by hand.

The classes it then showed had the wrong times: Monday 11:00 am, Wednesday 8:00 pm and Friday 9:00 am, against the brief's Monday and Wednesday 7:00 am, Tuesday and Thursday 6:00 pm and Saturday 9:00 am. One prompt (S1) fixed the capacities to 8, 12 and 6 and the lengths to 50, 45 and 55 minutes.

  • Payments and emails (C24 to C29) were not run: they need your own keys.
T03

Sign-in & Access Control

4/5Tested
Method
Sign-up and log-in for two members and the admin, then two attacks on the live app with the wrong role: a member looking for other members' bookings, and a member opening the admin page.
Attacks blocked
2 of 2
Log-in method
emailed code
Weak spot
new sign-ups get no role
Remark
Every flow works and both attacks are blocked, with one weak spot the tool could fix (new sign-ups get no role): 4.

Softr test app: a Permission denied page, with the text You don't have permission to view this page and a Back to home button.

Softr test app: a Permission denied page, with the text You don't have permission to view this page and a Back to home button.
T03-1 A member opening the admin page.
Raw notes

Sign-up and log-in for two members and the admin, then two attacks on the live app with the wrong role: a member looking for other members' bookings, and a member opening the admin page.

Log-in has no password. You give an email and Softr sends a one-time code. Sign-up and log-in worked for both members and the admin, and a log-in took 20 to 105 seconds from asking for the code to being in. The emailed code stands in for a password reset.

Attack 1 was blocked: a member sees no list of bookings, though the home counter shows the studio's total to everyone. Attack 2 was blocked: a member who opened /admin got a Permission denied page.

There is one weak spot. A new sign-up gets no user group, and the roles exist only on the invented sample users, so the instructor role cannot be tried. The Users tab holds 12 users, ten of them sample users that Softr created.

  • Softr's own security tools were not opened.
T04

Database & Admin

4/5Tested
Method
The six data checks: the form and bookings write real records, they survive a reload, a republish and a design change, the admin can view, edit and delete them, and they export as a file.
Checks proved
5 of 6
Remark
Five of six proved is 4.

Softr Data view with the Classes table showing zero records, after I deleted the invented classes, and the chat on the left saying it generated 72 sample records.

Softr Data view with the Classes table showing zero records, after I deleted the invented classes, and the chat on the left saying it generated 72 sample records.
T04-1 The Data view with the Classes table emptied by hand.
Raw notes

The six data checks: the form and bookings write real records, they survive a reload, a republish and a design change, the admin can view, edit and delete them, and they export as a file.

Verified (five): the Ask the studio form wrote a record (inquiries went from 8 to 9); records stayed after reloads, several republishes and the dark colour change; the admin added, edited and deleted classes in the Data view and in the app; and the bookings exported as a CSV file, although its class columns were blank.

Not verified: bookings written by a member. Members have no Book button, so the bookings table only holds the 32 invented sample rows. The plan page counts the records against 1,000,000 included.

  • Backup and restore were not opened.
T05

Iteration & Credit Burn

2/5Tested
Method
The twelve scripted changes, one prompt each, then the live app opened to see whether the change had happened.
Changes that worked
5 of 12
AI credits for the twelve
about 5
Remark
5 of 12 working is the 2 band (3 to 5).

Softr test app as the admin sees it, in dark green and cream, with the About link in the menu, a dark mode button at the top right, three class cards and counters for classes, bookings and inquiries.

Softr test app as the admin sees it, in dark green and cream, with the About link in the menu, a dark mode button at the top right, three class cards and counters for classes, bookings and inquiries.
T05-1 The app after the colour, capacity, dark mode and About page changes.
Raw notes

The twelve scripted changes, one prompt each, then the live app opened to see whether the change had happened.

5 of the 12 worked: the dark green and cream colours (E03), Power Reformer capacity 4 (E05), the phone layout (E09), the bookings export on the admin page only (E10) and a dark mode toggle with the data intact (E12).

7 did not: no phone field on sign-up (E01), Coach and Instructor both still showing (E02), an About page whose address, phone and email are invented instead of the brief's (E04), no instructor filter (E06), no credits or cancel flow (E07), no second email (E08) and no waiting list (E11).

Each prompt finished in about one minute or timed out after 12 minutes. The twelve changes used about 5 AI credits.

  • Fixes after a failed change were not tried.
T06

Publish, Speed & Mobile

3/5Tested
Method
Publish to the vendor address, timed, then a Lighthouse phone run on the home page of https://clifton69332.softr.app.
Time to publish
5 s
Phone speed score
63
Largest paint
9.0 s
Page weight
1.4 MB
Remark
A score of 63 is in the 50 to 74 band: 3. The app is on the vendor address only, which is also 3.

Softr editor with the dialog Your app is live showing the address clifton69332.softr.app and the buttons Keep building and See it live.

Softr editor with the dialog Your app is live showing the address clifton69332.softr.app and the buttons Keep building and See it live.
T06-1 The dialog after Publish.
Raw notes

Publish to the vendor address, timed, then a Lighthouse phone run on the home page of https://clifton69332.softr.app.

The Publish button opened a dialog and the app was live in 5 seconds on its softr.app address. A "Made with Softr" badge shows on the live app, on the Business trial.

The phone score was 63. The largest contentful paint was 9.0 seconds and the page weighs about 1.4 MB.

A custom domain, a timetable with 100 seeded classes, layout faults at three widths and a real phone were not tested.

  • Home page only; no domain; no layout fault count.
T07

Export & Ownership

1/5Tested
Method
Looking for a way to take the app out: the export options in Settings and in the Data view.
Code export found
none
Remark
No code export: 1.
Raw notes

Looking for a way to take the app out: the export options in Settings and in the Data view.

I found no option to export the code or the app in Settings or in the Data view. What exists is a CSV of the records and a CSV of the bookings from the admin page. I did not read the terms.

  • Settings and the Data view only.
T08

Pricing & Cost to Finish

3/5Tested
Method
The plan and billing page and the pricing modal were read on 26 October 2026 (monthly view).
Paid
$0
AI credits used
about 8.8 of about 54
Remark
Needed a plan above Free to get this far, and the cost to finish does not exist because the app never finished: 3 (a top-up was needed and the running cost is unclear).

Softr Plan and billing page: Business (Trial) with the trial ending on November 1, 2026, and the apps, databases and workflow usage panels.

Softr Plan and billing page: Business (Trial) with the trial ending on November 1, 2026, and the apps, databases and workflow usage panels.
T08-1 The plan and billing page.
Raw notes

The plan and billing page and the pricing modal were read on 26 October 2026 (monthly view). Softr shows AI credits, not a price per prompt.

I paid nothing: the workspace was a Business trial with no card. AI credits read 53.95 before the first fix prompt and 45.2 after the twelve changes, so about 8.8 were used. The trial ends on 1 November 2026 and the workspace then falls back to Free.

Modal prices, monthly: Free (5 AI credits a month), Basic $25 (10), Pro $119 (50), Business $395 (100). The Free plan's 5 credits would not have covered the test, and Basic's 10 would only just have. The app never reached a finished state, so the price of a finished app cannot be stated.

  • Trial credits are not a plan's real allowance. Yearly prices were not read.

Coverage

Tested

  • One brief built through the wizard, then 13 follow-up prompts and a clean-up by hand in the Data view
  • 24 of the 30 written checks (C24 to C29 need keys), run on the live app
  • Two access attacks on the live app
  • Sign-up and log-in by emailed code for two members and the admin
  • The twelve changes, one at a time
  • Publishing to the softr.app address, timed, and a phone speed run
  • The settings and data screens, looking for a code export
  • The plan and billing page and the pricing modal

Not tested or limited

  • Payments and emails were not tried because they need your own keys (C24 to C29)
  • Support: my question in Softr's live chat (26 October 2026, 08:51 UTC) had no reply when this was written
  • The instructor screens were not reached: new sign-ups get no user group, and I could not sign in as one of the sample instructors
  • Speed was measured on the home page only, with no layout faults counted and no real phone
  • No custom domain was connected and the terms of service were not read
  • I looked for a code export in Settings and in the Data view only

Still to test

  • Payments and emails with your own keys
  • Softr's answer to my support question
  • A custom domain and a timetable with 100 seeded classes
  • Layout faults at three widths and on a real phone
  • Setting up user groups by hand so the coach screens can be tried
  • Uptime on the test app
What these results meanRead the full Softr review