Skip to content

Playground screenshots, the pain points readers voice, performance, community - #7

Merged
oblomov-dev merged 21 commits into
mainfrom
claude/friendly-wright-oeyc4s
Oct 29, 2026
Merged

oblomov-dev merged 21 commits into
mainfrom
claude/friendly-wright-oeyc4s

Conversation

@oblomov-dev

Copy link
Copy Markdown
Member

What this changes

The follow-ups pushed after abap2UI5/why#6 was merged. main is merged in; the diff against it is only these commits.

Screenshots from the playground

  • The hero shows the sales-orders app with its Explain This Data panel open, rendered from the playground at 2x.
  • The eight use-case cards are re-rendered the same way, cropped to their content and to 2:1, so a card shows a filled screen rather than the empty canvas under a short one. The card box is 2:1, anchored top centre.

The pain points readers voice most (from SAP Community, DSAG, consultancy blogs 2024 to 2026)

  • Comparison row Time to productivity: an afternoon for an ABAP developer against weeks of CDS, RAP, annotations and tooling.
  • The team is ABAP adds "no training project before the S/4HANA project" and the honest line that developers still learn UI5's controls, from the examples, not a new language.
  • FAQ Our users are fast in SAP GUI. Will they accept it?: one request per click on the same ABAP stack, one screen at a time, the GUI stays until the last one.
  • The example catalogue in figures: 130 learning samples and 680 control examples, each running in the browser.
  • Free to leave: the skill a team invests in is ABAP, the one it keeps.

Performance

  • Comparison row What a click costs: one plain HTTP request with the changed data only, no app code or logic in the browser, against OData, batch, draft handling and runtimes in the browser.
  • A reason It is fast where users notice, and the FAQ answer starts with "Faster than most Fiori apps, in practice" and names the mechanism.

Join the community (new section, in the navigation)

  • Open source and it stays that way (MIT, no owner who could close it), help in public, built on abapGit and abaplint and worth supporting, add-ons to share, a post on LinkedIn, sponsoring. Replaces the giving-back strip.

Who runs it

  • Moves down, after the FAQ. Says that many more installations exist than the list shows, and ends with a dashed Your company here card: one row by pull request or by mail.

Smaller

  • Slack in the footer. The note under the hero buttons is gone.
  • The word limit in the test moves from 2,600 to 2,800 for the new section; the page sits just under it after trimming duplicates and one redundant governance row.

npm run check passes (8 tests).

Still open

abap2UI5/docs#387 points the manual at /why/ and can be merged now that the page builds under its new path.


Generated by Claude Code

claude added 21 commits October 29, 2026 06:41
Half the length, proof before the pitch, the downsides next to the
upsides: what a decision maker checks first, in the order they check it.

- Order: use cases, who runs it, where it fits and where it does not,
  governance, cost, platform, AI, FAQ, get started. Add-ons dropped (a
  developer topic, linked), No strings folded into Cost, the week and the
  ways in merged into one closing block.
- Who runs it: "In production" and "Partner" tags instead of ABAP release
  numbers, the figures a reader can check (since December 2022, 25+
  contributors, release 1.148 in October 2026) with their source; the
  five references a manager recognizes first, the other fifteen folded.
- Comparison: three rows where abap2UI5 is not ahead (standard
  transactional apps, offline and real-time, support), a "Where something
  else fits better" box next to the reasons, and no superlative headings.
- Support, as SUPPORT.md states it: community, best effort, no support
  contract on offer today; the FAQ and the cost sheet say so.
- Cost: a five-line sheet (three zeros, developer time, partner services)
  beside the price card; the calculator folds under a summary; the
  giving-back note moves to a short strip before the foot.
- Hero: the grid-table example in the current theme instead of the grey
  walkthrough; the primary action opens the example apps, not the
  playground sandbox.
- Platform in manager terms: no ICF, sy-uname or user exit in the text.
- Mobile: the section links stay as a scrolling row under the header; a
  comparison row becomes a card with the column name on every cell.
- Footer: build date and the contact address.
- Tests: the visible text stays under 2,600 words, the comparison keeps
  its even rows and the support wording, every <td> carries data-th.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
The company no longer exists: its row under Who runs it and its 2024
blog reference go. Logali Group is tagged Training, and the cost sheet,
the fit box and the FAQ name training and certification instead of
partners.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
Live data on a connected screen is what the framework does; a device
without a network is what it is not for.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
Support is an issue or a pull request on GitHub, from anyone, at any
time, and that is the channel to prefer: transparent, and where answers
reach everybody. An organization that needs more writes to the
maintainers. What is not on offer is an SLA in a contract; "no support"
and "best effort" are gone, and the test refuses them.

The header button says Try it out and opens the playground; the hero
keeps the example apps.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
One faint brand wash on the hero and the closing band instead of coral,
sky and mint; the headline accent in solid brand red instead of a red to
orange gradient; the figures in ink with the price as the one accent;
the price card dark instead of an orange gradient; neutral dots on the
window bar; the giving-back strip on the grey band. The brand red stays
for buttons, kickers and one accent per block.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
Anyone can write in the Slack channel or open a GitHub issue at any
time; the ways in get a Slack door and a mail door for more, planned
together.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
The hero shows the sales-orders app with its Explain This Data panel
open, rendered from the playground at 2x. The eight use-case cards are
re-rendered the same way, cropped to 2:1 and to their content, so the
box shows a filled screen rather than the empty canvas under a short
one; the card box is 2:1, anchored top centre.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
From a look at what SAP Community, user groups and consultancies name
in 2024 to 2026: a comparison row on time to productivity (an afternoon
against weeks of CDS, RAP and tooling), no training project before the
S/4HANA project and the honest line that developers still learn UI5's
controls, a FAQ on user acceptance after SAP GUI, the example catalogue
in figures, and the skill a team keeps.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
A comparison row on what a click costs, a reason in "Why teams choose"
and a sharper FAQ answer: no frontend logic, no OData, no app bundle,
the generic shell loaded once, the changed data only.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
The performance point pushed it over; the duplicates around it go,
and the governance table loses its one redundant row.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
A section on the open-source side: MIT and no owner who could close
it, help in public, abapGit and abaplint underneath and worth
supporting, add-ons to share, a post on LinkedIn, sponsoring. It
replaces the giving-back strip and joins the navigation.

Who runs it says that many more installations exist than the list
shows, and ends with a dashed "Your company here" card: one row by
pull request or by mail.

The word limit moves to 2,800 for the new section.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
The bands re-alternate, the navigation follows, and the FAQ answer
links down to it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014YZFmDmGbnnhTHeXMxMCrJ
@oblomov-dev
oblomov-dev merged commit 9d68134 into main Oct 29, 2026
2 checks passed
@oblomov-dev
oblomov-dev deleted the claude/friendly-wright-oeyc4s branch October 29, 2026 10:09
oblomov-dev pushed a commit that referenced this pull request Oct 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants