A login button earns its place when it helps a visitor do something useful: resume a lesson, recover a reading list, or continue a small draft on another device. Begin with that outcome. Then decide whether hosted sign-in matches the people who use your product and the support your business can provide.
This guide helps founders and product teams make that decision and define a practical rollout. For implementation details, use the passwordless authentication API guide.
What passwordless website login means here
In this guide, passwordless means your application does not ask customers to create or manage an application-specific password. A visitor completes the hosted Gammal Tech sign-in popup. Your website confirms the session and loads only the information its own project previously saved for that account.
Customers reuse their one Gammal Tech account across participating websites. A new customer registers once with identity verification; Gammal Tech permits one account per person. This is a hosted account experience, and this guide does not promise a particular login-code delivery channel or a biometric sign-in method.
Your app therefore has no customer password database or app-specific password-reset flow for this integration. Account access questions can still happen. The website also handles a sensitive session token, so removing application passwords does not remove session protection or other security responsibilities.
Match sign-in to a meaningful customer benefit
Write the benefit beside the action that requires login. “Sign in to keep your reading list” gives a visitor a reason to continue. Asking for an account before explaining the product leaves them to guess why it is necessary.
| Customer need | What to evaluate |
|---|---|
| Resume learning | Save lesson progress and bookmarks. Decide what someone can preview before signing in and what “resume” should show. |
| Continue productive work | Restore settings and small drafts. Check that the information fits within the 1 MB per-user storage limit. |
| Use a customer portal | Provide a clear signed-in starting point. Separately establish which business records the customer may access. |
| Complete an immediate one-off task | Ask whether an account is needed at all. If it is required, assess the first-account verification journey before promising immediate access. |
A service with many existing Gammal Tech users has a different onboarding situation from a service whose visitors are all new to the account system. Test both groups. Neither a familiar brand nor fewer password fields establishes that everyone will finish faster.
For an existing site, also confirm how previous customer records will connect to the new experience. Reusing a Gammal Tech account does not automatically migrate purchases, permissions, or records from another system. The website authentication architecture guide covers account migration and linking.
Design separate first-time and returning journeys
For an existing account holder
- Explain the immediate benefit. Keep the sign-in action beside the feature the customer wants to use.
- Open the hosted sign-in flow. Make clear that the popup belongs to Gammal Tech and that an existing account can be reused.
- Confirm sign-in and load saved work. Show a loading state until the website knows which information is available.
- Return to the intended task. A reader who selected “save this article” should return to that article, with the resulting save status clearly shown.
- Keep sign-out visible. After signing out, remove the signed-in account view, particularly on shared devices.
For someone creating their first account
Explain the verification requirement before sending the person into registration. Applicants of any nationality use a National ID issued by a country whose citizenship they hold, rather than an identity card issued solely because they reside elsewhere.
The exceptions are an Egyptian passport for Egyptian citizens living abroad who do not have their Egyptian National ID available, and an Egyptian birth certificate for Egyptian citizens living in Egypt who are under 15 and have neither an Egyptian National ID nor a passport. The documents are submitted to Gammal Tech, not to your website.
First registration and returning sign-in are different tasks. Avoid describing the entire first-account journey as instant or assuming every visitor already has an approved account. Give newcomers an explanation of what they can do while registration or verification is incomplete, such as reading public guidance or returning later to continue.
For a returning visit or another device
Sessions are kept per browser tab. Opening a fresh tab or reopening the browser requires sign-in again. A new login produces a different session token; it is not a permanent customer identifier. After the same account signs in, the project can retrieve its previously saved information across visits and devices.
Signing out ends the local session; it does not delete saved preferences. Explain this distinction where users might confuse “sign out” with “delete my data.” The separate session and saved-data guide covers the underlying behavior.
Tell customers what your website receives
Gammal Tech does not disclose the underlying account name, email address, phone number, National ID number, or identity documents to developers. There is no identity lookup for your website to call. Your project retrieves only the data it previously saved for that account.
If your own form asks a visitor for a display name or contact information, that is a separate collection by your business. Explain its purpose and distinguish it from the private account verification information. A signed-in customer should not be told their contact details came from Gammal Tech.
For example, a reading service can remember bookmarks and a chosen reading preference without receiving the account holder's verified identity. A delivery business may need an address through its own order form. The login feature does not supply that address or decide how the business should handle it.
Make cancellation, loading and accessibility part of the design
Successful sign-in is only one state. If the customer closes the popup, keep the original page usable and offer a clear way to try again. If a popup is blocked, give simple instructions for the action needed. If account data cannot be loaded, do not show empty defaults as if the customer's saved work never existed.
For controls your team builds, provide clear names, visible keyboard focus, and a logical return point after the popup closes. Test the journey with keyboard navigation, a screen reader, browser zoom, and a narrow mobile screen. Include both the website and the hosted step in the review.
W3C's accessible authentication guidance explains why authentication should not unnecessarily depend on memory or transcription. Where a code must be entered, support paste and suitable assistive mechanisms. Assess the complete experience before making an accessibility conformance claim.
A useful acceptance task is: “On a shared computer, sign in, recover a bookmark, sign out, and explain what another person can now see.” This tests whether the customer's understanding matches the actual page state.
Set up the project and budget for code usage
The owner starts with a verified Gammal Tech account and creates a project in the Developer Console. Browser API access uses a public project identifier and domain whitelisting, without a secret API key. Each project supports up to four registered HTTPS domains; the bare domain and its www version count separately.
| Item | What to budget |
|---|---|
| Login, logout and session checks | Free, with unlimited use. |
| Saved user data | Free, with a maximum of 1 MB per user. |
| Login codes (OTP) | 200 codes per project per month are included; additional codes cost 0.40 EGP each. |
| Project creation | The first project is free. Additional projects have a one-time fee shown in the Console. |
The OTP allowance covers codes sent during login and checkout identity verification and resets monthly. Paid usage uses the project balance: add funds to the personal wallet, then transfer funds into the project. Count codes actually sent when estimating costs, rather than equating visitors, active accounts, or sessions with billable codes.
Historical currency illustration: 0.40 EGP was approximately US$0.0077 using USD 1 = EGP 51.78, the midpoint previously recorded from Banque Misr's buying and selling rates on 24 September 2026. This is the earlier article's dated illustration, not a current exchange-rate quote. EGP is the billing amount; payment-provider rates and fees can differ.
Use the authentication-code pricing comparison for message-cost calculations, or the Firebase authentication pricing comparison when choosing between account-service models.
Measure whether the experience is better for your customers
Before launch, define the customer outcome, a measurement period, and what improvement would justify a wider rollout. Compare equivalent tasks and report first-time registration separately from returning sign-in. These are proposed evaluation measures, not claims about results already achieved.
| Measure | Useful interpretation |
|---|---|
| Returning sign-in completion | Completed sign-ins divided by sign-in attempts among existing account holders. Track cancellations separately from technical failures. |
| First-account completion | People who complete the required registration and verification journey out of those who begin it, using an appropriate follow-up period. |
| Task completion | Can a signed-in customer actually restore the draft or bookmark they came for? Login success alone does not answer this. |
| Support and operating effort | Account-access requests, failed restores, staff time and OTP usage during comparable periods. |
Keep analytics limited to appropriate aggregate events; do not put session tokens, identity documents, or sensitive saved content into analytics. Look at mobile and desktop results separately. A useful change reduces friction in a real customer task without hiding a new difficulty in registration, recovery, or support.
Common questions about choosing hosted login
Do customers need a new password or account for each website?
No application-specific password or additional Gammal Tech account is required for each participating website. Customers reuse their single Gammal Tech account through hosted sign-in.
Can customers keep their progress across devices?
Yes. After the same account signs in, your project can retrieve its previously saved data, within the 1 MB per-user limit. The project cannot request another application's saved data.
Does this remove all support and security work?
No. Your application avoids maintaining its own password storage and password-reset flow for this integration. It still needs safe session handling, appropriate product permissions, customer support, and a reliable signed-in experience.
Can a successful login unlock any paid or administrative feature?
Only if a separate, trustworthy permission decision allows it. Authentication confirms the session; it does not establish purchase history, a staff role, or access to a private business record.
References and scope
Product facts were checked against the published documentation on 14 October 2026. The journey examples and pilot measures are planning recommendations, not measured customer results.
- Gammal Tech integration reference: registration, privacy, domains, session behavior, storage and account-service pricing.
- W3C: Accessible Authentication (Minimum): authentication accessibility guidance.