דילוג לתוכן
מרכז התיעוד
לאתר LinkNodes Energy
LinkNodesENERGYתיעוד

טוענים את החיפוש…

    חיפוש גם בתוך המאמרים ↑ ↓ לניווט Esc לסגירה

    לאתר החברה

    מובייל ופלטפורמות

    טיוטה: חוויית המובייל הנייטיבית

    תיעוד שינויי מסכים, פעולות ובדיקות בשחרור הפיתוח מ־20 בנובמבר.

    בעמוד הזה

    Scope and baseline#

    This change implements the requested mobile interface pass against the supplied iPhone screenshots and recording. Source baseline: e2f866f269072321466c59ace00b3777497477cf (Google login preview, PR #64). Working branch: mobile/native-experience-20261120, stacked on mobile/google-login-20261120.

    The existing purple, navy and lime palette, LinkNodes mark, approved vehicle artwork, account identity, server permission rules and website remain the source of truth. Changes are confined to the Expo application, focused regression tests and this document. No package, lockfile, native runtime, API contract, database, billing integration or production website changes are included.

    Implemented screens and actions#

    SurfaceNative behaviorExisting website continuation
    HomeCompact workspace switcher, personal greeting, four quick actions, truthful vehicle/provider counts, recent activity detail sheet and refreshRole-specific management hub
    MapViewport-sized map, current foreground location, approved selected-vehicle marker, search within returned viewport, provider/fast filters, station list/details, explicit directions handoff, recenter and location recoveryAuthorized provider selection
    VehiclesAuthorized vehicle collection, catalog artwork, search, status, budget, detail sheet and refreshAdd/edit/manage vehicles for fleet-write roles
    EnergyCurrent/previous month and 90-day ranges in the workspace timezone, charging/fuel filters, search, item details, progressive display of all returned records, partial and unverified-data statesReports, import/export and authorized billing
    ProvidersSelected providers, connection status, energy filters, search, detail sheet and validated HTTPS provider website linksProvider selection for fleet-write roles
    AccountIdentity summary, first/last-name editing, workspace switching, plan/role labels, contextual provisioning sheet, support/legal links, sign-out and deliberate deletion-request sheetAccount preferences, plan settings and authorized support
    ManagementRole-filtered list of real management destinations with explicit website labelsVehicles, providers, energy, analytics, billing, drivers, policy, credentials, team, audit and settings, as permitted
    LoginCompact form, native keyboard/autofill behavior, accessible controls and the existing Google, password, verification and reset flowsExisting Clerk hosted Google flow

    The five main tabs remain stable. Hidden Providers and Management routes retain navigation history, so Back returns to the originating tab. The tab bar respects the device bottom inset and text scale. Native sheets provide scrolling, keyboard avoidance and a close button; dismissal is disabled while an account mutation is in flight.

    Shared controls use at least 44-point targets, 48-point primary actions, existing color tokens and right-aligned Hebrew text. Screen titles and workspace cards are compact instead of repeating a large dashboard hero. Loading/error copy is written for the customer; runtime integration diagnostics are removed from Account.

    Plans, roles and device surfaces#

    Account / roleMobile experienceManagement scope
    Personal / FamilyHome, map, vehicles, providers, energy and account workflowsExisting desktop/responsive website for advanced management
    Business / Enterprise driverAssigned vehicles from existing server/RLS scope, map, selected suppliers and own accountNo organization spending request or management action
    Business / Enterprise fleet managerFleet visibility, providers and energy reportsVehicle/provider management, drivers, policy and credential records; no billing or member administration
    Business / Enterprise financeOrganization fleet read access and energy/billing visibilityNo vehicle/provider write action or team administration
    Business / Enterprise adminOperational management, reports, billing and organization settingsTeam/audit viewing; no owner-only membership administration
    Business / Enterprise ownerAll relevant native daily-use surfaces and management destinationsOwner-only membership administration and plan changes remain owner-only

    Enterprise retains the same server role boundaries; the plan name never grants administrative power. Its primary management surface remains the website. Personal and Business continue to use the existing desktop interface. This release does not redesign that interface.

    Native client mutations currently cover account provisioning and deletion requests; profile names use the existing Clerk SDK. The client API has no native vehicle, provider-selection or team mutation endpoints. Those operations are therefore explicit website continuations, rather than simulated native saves. A browser may require a separate sign-in; no tokens are included in URLs.

    Data and state corrections#

    • Resource requests use the existing stable Clerk token getter. Changing a render wrapper no longer restarts every request and leaves Vehicles/Energy loading indefinitely.
    • Results are scoped to user, active tenant and the complete resource/date query. A changed scope hides old data immediately, aborts superseded requests and rejects late/wrong-scope responses.
    • Initial loading, refresh, failure and successful empty results have distinct states. A failed request does not become a successful empty report.
    • Map location/request lifecycle and approved-image validation are preserved. The map mounts only for a valid active access context. Location is a phone position, not vehicle telemetry; no background tracking was added.
    • Provider counts describe selected providers. Sandbox, unavailable and unconnected integrations are not presented as live charging/payment capability.
    • Financial summaries retain minor units and partial-result warnings. Imported/platform records are identified as unverified, not invoices or proof of payment.
    • Calendar dates such as YYYY-MM-DD retain the intended day; timestamp display follows the workspace timezone.
    • Workspace selection is disabled while its context refresh is active, preventing a late refresh from undoing a newer choice through the new switcher.
    • Provisioning keeps its persisted idempotency key until the created workspace is visible in fresh context. A failed context refresh can be retried without another provisioning POST.
    • Profile/deletion/provisioning forms prevent duplicate submissions, reject stale identity completions and hold sheet dismissal while a write is active. Deletion retains the original destructive confirmation and legal-retention disclosure.

    Verification#

    Run from apps/mobile using the installed dependencies:

    node node_modules/typescript/bin/tsc --noEmit
    node --experimental-strip-types --test scripts/*.test.mjs
    

    Both commands passed for this change. The complete suite contains 121 passing tests covering authentication, foreground map lifecycle, workspace/request races, all 20 plan/role combinations, website route boundaries, presentation helpers, account mutations/idempotency and release configuration. Tests use synthetic data and mocked mutation boundaries; no real profile updates, organizations or deletion requests were created during QA.

    The authentication handlers preceding the screen JSX are byte-identical to the PR #64 baseline. The 13 Google/password/signup/reset regression tests still pass.

    Unchanged SHA-256 values:

    FileSHA-256
    apps/mobile/app.json8a828cdc53b1d27f639bc5d259f1c60c41eeb59eca29d32f6fc8932baaa1c24d
    apps/mobile/package.json8230b49f2c2e1e26b4ec51349ada9c100faf00d209691d3ec84cf7da7338caf2
    pnpm-lock.yaml1c81b81a5fe1d86b0395753097450796de95c7b3458d88a056b3294db9b54ee9

    A local RNWeb harness imports the actual screens with synthetic identity/data fixtures. It compiled, but screenshots/geometry could not be produced: local Chromium could not open its required socket, and the separate cloud browser could not reach the local server. This is not physical iOS, rendered visual, VoiceOver or Dynamic Type verification. Those checks remain part of device acceptance below.

    iPhone preview and acceptance#

    The authorized delivery target is the existing iphone-preview branch, preview EAS environment, iOS only, project [expo-project-id-redacted], runtime 0.1.0. Publication metadata and its exact source commit are recorded on the PR after the export/upload succeeds. A published Expo Go update is not a TestFlight/store-signed binary or App Store submission.

    The blue floating gear in the supplied recording belongs to Expo Go's Tools UI. SDK 58 documents __expo_disable_fab=1 and __expo_disable_auto_launch=1 launch parameters. They hide the developer overlay for that launch without changing product assets or persistent developer settings: Expo launch URL documentation.

    Device acceptance should check:

    1. Open the exact newly published update; verify the compact Home and five tabs.
    2. Verify Google and password sign-in, including cancellation returning safely to the form.
    3. Open Map with location allowed and denied; check current-location framing, approved vehicle image, station selection, filter/list controls and directions.
    4. Search Vehicles/Providers, open details, pull to refresh and recover from a connection failure.
    5. Switch between authorized workspaces; verify role labels/actions and that prior-workspace data never appears.
    6. As a driver, verify assigned vehicles and map/supplier actions without organization financial data. As an authorized manager, verify the explicit website handoffs and Back behavior.
    7. Edit a profile name, confirm the sheet stays open during saving, and verify the new name after success. Do not create organizations or request deletion merely for a visual check.
    8. Check a smaller iPhone, increased text size, keyboard, safe areas and VoiceOver on the actual device.

    Rollback and remaining integration limits#

    The last known published baseline is Expo group 35b151df-1f9d-4d2e-a528-735b2dffa037, iOS update 01a1fa74-ccb2-77c2-80de-a191a4715cf3, source e2f866f269072321466c59ace00b3777497477cf. If device testing identifies a regression, reopen that exact preview or republish that existing known-good artifact to iphone-preview; do not regenerate the visual design as a repair.

    Real provider activation, charging execution, settlement/invoices, native advanced-management mutations, Enterprise SSO/SCIM and store signing are not established by this UI release. Existing external-credential and enrollment dependencies remain separate. CI/merge approval is also separate from a successful local suite and authorized Expo preview; do not bypass repository checks to merge this branch.