Demo · 7 September 2026

Angular / Ionic

Schedule, filters and edit forms. On desktop the app sits in a phone frame; on mobile it fills the screen. Data is local test data; the scheduling backend is not connected.

The repository contains a source snapshot dated 1 May 2024; this does not establish when development began. Demo: 7 September 2026.Version 71ea9d0d13 interface screenshots

01 / The task

Schedule and tables in Angular / Ionic

A record is selected from the table and edited in a form. Cancelling must leave the original record unchanged. The table needs to recalculate its size after Ionic navigation.

Use case: Working with schedules and records in tables.

Work done

  • Phone frame, login screen and URL synchronization with the iframe.
  • Table resizing after Ionic navigation.
  • Filters, forms, statuses and mobile layout.
  • Record ID and duplicate-add fixes. Separate demo login and test dataset.

Screenshots

Screens, forms, errors

Screenshots, diagrams and source evidence retain their original language; captions and descriptions are translated.

02 / Technology

Stack

Angular 17

Page components, forms, routing and state.

Ionic 7

Navigation, controls, modal forms and a responsive interface.

SlickGrid

Tabular views and row operations.

03 / Decisions

How the project works

  • Synthetic records cover the demonstrated fields instead of replacing the table with an empty mockup.
  • The form edits a draft; canceling must leave the original record unchanged.
  • Changes stay within the browser session; the public demo is not connected to the scheduling server API.
Components of the published demo
Components of the published demo

04 / Verification

Demo workflows

  1. Sign in with test / test and open the schedule.
  2. Filter records, switch statuses and compare views.
  3. Add a record, check required fields, open the editor and cancel a change.
  4. Check the mobile view and reset the original dataset.

Check results

  • 13 meaningful screenshots of the actual interface retained.
  • Each screenshot includes its date, scenario and code revision.
  • No separate backend process runs on the VPS: Nginx serves static files. Shared Nginx resources cannot fairly be attributed to a single site.
  • 6 scenario repetitions measured; median 2390.0 ms, maximum 3282 ms. Timing includes the browser and HTTPS; methodology and limitations are included.

Limitations

  • Demo credentials test / test are not an authentication system.
  • 180 synthetic laboratory records and four BCP examples are not production data.
  • Unimplemented sections are excluded from the demo navigation. Added rows are limited to 500.

Technical notes

Modules, API, data model, setup and check results.

Documentation →Materials ↓