Project progress

Alammaya,
piece by piece.

A clear view of the mobile app’s journey—from an idea, through careful checks, to a useful module in your pocket.

As of

01

One careful path for every module

Each module follows the same 13 stages. The eight green checkpoints are where the project owner approves the work before it moves on.

The 13-stage module lifecycle with 8 owner approval gates Stages run from brainstorm to tester distribution. Gates follow stages 2, 3, 4, 6, 7, 8, 10 and 11. Defect fixing loops back to device checking. The 13-stage module lifecycle with 8 owner approval gates Stages run from brainstorm to tester distribution. Gates follow stages 2, 3, 4, 6, 7, 8, 10 and 11. Defect fixing loops back to device checking.

Quality loop: if the device check finds a problem, stage 11 fixes it. After owner approval, the module returns to stage 10 for another check.

02

Where each module stands

Every module travels the same 13 stages, grouped below into five phases. Read a row left to right to follow its journey. The small green diamond ◆ on a column marks one of the eight owner gates. On a phone, each module becomes a card you can open.

    Filter rows

    Reading the table: scroll it sideways to see all 13 stages — the module column and the headings stay in place. A green diamond ◆ marks an owner gate.

    Module progress by lifecycle stage. A green diamond ◆ in the column heading marks an owner gate. Stage 13 (tester distribution) is shared across the whole app.

    Platforms and tester channels

    03

    How the app fits together

    The phone never talks to the business system directly. A small, secure gateway passes along only the information each screen needs.

    Sign-in, without a password

    Each tester receives a demo-user API key and pastes it into the app. The key identifies the demo user and what that user may see.

    The app never asks for an Odoo password. Keys stay private and are cleared from the sign-in field after use. A one-time sign-in code (spec and design approved) will make first-time setup even simpler.

    Where tester builds come from

    iPhone: Apple’s TestFlight app delivers the invitation and installs the build. This channel is live.

    Android: testers receive a separate invitation with a download link. No app-store account is needed for this testing round.

    04

    What is happening now—and next

    The short version: Repair is building its Android screens, the one-time sign-in code is being documented after approved spec and design, the finished modules are being polished, and both tester channels are live.

    05

    Your guide to testing

    Everything in the app is demo data on a training copy. The app only reads information; you cannot change anything in Odoo from it.

    iPhone tester guideTestFlight · 5 short steps · tap to open

    You are testing the Alammaya mobile app on an iPhone. Use the same Apple ID throughout the invitation and installation. Everything you see is demo data, and the app only reads information.

    1. Accept the invitation (once)

    1. Open the invitation from Apple App Store Connect and accept it. Sign in with the same Apple ID that received the invitation.
    2. When Apple asks about two-step verification or agreements, follow the prompts.
    3. Tell the project owner that you accepted, then wait for the “You’re invited to test” message from TestFlight.

    2. Install the app

    1. On the iPhone, install TestFlight from the App Store. The iPhone needs iOS 16.4 or later.
    2. Open TestFlight, sign in with the same Apple ID, and tap View in TestFlight in the invitation (or find alammaya in the TestFlight app list).
    3. Tap Accept, then Install on alammaya.
    4. Open the app from the home screen.

    3. Sign in

    1. The app asks for a server and an API key. Leave the server address already shown in the app as it is.
    2. You will receive demo-user keys privately from the project owner. Copy one key and paste it into the API key field. The field hides the key.
    3. Tap Sign in. After a successful sign-in, the app clears the key from the field.
    4. To try another demo user later, sign out and paste a different key.

    Never type an Odoo password in the app. It has no password field. Do not share your keys, post them in chat, or include them in email.

    4. What to test

    • Open each module from All apps and look at the lists and detail screens.
    • Switch between demo users. The manager sees more modules than the plain user.
    • Turn on airplane mode briefly and check that the app says it is offline and recovers afterwards.
    • Make the text size larger in Settings > Display & Brightness > Text Size and check that nothing is cut off.
    • Rotate or background the app, then come back.

    5. Report what you find

    Send a short message to the project owner with what you did, what you expected, what you saw, the demo user you were using, and a screenshot.

    In TestFlight you can also tap the app and use Send Beta Feedback to send a screenshot and device information.

    Please never include a key or a password in a report.