Feature Request: Expanded Authentication Options for Better Accessibility, Scalability & User Adoption

Feature Requests
1

Dear Hercules Team,

I hope you are doing well.

First of all, I would like to appreciate the Hercules team for building such an innovative and highly capable platform. The product direction and engineering execution are genuinely impressive.

I would like to formally propose an enhancement regarding the platform’s authentication and login architecture.

Currently, the system relies heavily on email-based authentication workflows. While this model is technically sound and common across SaaS ecosystems, in real-world deployment environments — especially in emerging markets like South Sudan and other low-connectivity regions — it introduces operational friction that negatively impacts user experience, onboarding efficiency, and long-term adoption.

Many of our users have expressed concerns and dissatisfaction regarding the current login process. The primary issue is that email-dependent authentication creates unnecessary complexity in environments where internet speeds are inconsistent, latency is high, and email synchronization itself may already be unreliable.

Some of the recurring user pain points include:

  • Delayed or failed verification email delivery

  • Difficulty accessing inboxes under poor network conditions

  • Authentication interruptions during login sessions

  • Password reset dependency on external mail services

  • High onboarding abandonment rates

  • Increased support requests related to account access

From both a technical and business perspective, introducing multiple authentication options would significantly improve the platform’s accessibility and scalability.

Modern global platforms have already evolved beyond strict email-only authentication models. For example:

  • Facebook allows users to log in using:

    • Username

    • Email

    • Phone number

  • Instagram supports:

    • Username/password login

    • Phone authentication

    • Email authentication

  • X (Twitter) uses:

    • Username or email-based login

    • Flexible recovery systems

  • LinkedIn supports:

    • Email authentication

    • Persistent trusted-device sessions

    • Social sign-ins

  • Google Gmail itself goes beyond email dependency by integrating:

    • Device authentication

    • Passkeys

    • Recovery numbers

    • Authenticator-based flows

    • Multi-device session persistence

These systems are designed around a core UX principle:
Reduce authentication friction while maintaining security.

This is especially important for platforms targeting rapid growth, international adoption, and mobile-first users.

I strongly believe Hercules would benefit immensely from implementing a hybrid authentication architecture that supports:

  1. Username + Password Login
    Allow users to create memorable usernames and authenticate directly without relying on email every time.

  2. Multi-Identifier Authentication
    Enable login using:

  • Username

  • Email

  • Phone number

  1. Session Persistence Optimization
    Allow secure long-duration login sessions for trusted devices to reduce repeated authentication requests in low-bandwidth environments.

  2. Flexible Recovery Systems
    Offer alternatives such as:

  • SMS recovery

  • Authenticator apps

  • Backup recovery codes

  • Trusted device verification

  1. Lightweight Authentication Infrastructure
    Reducing dependency on repeated real-time email verification calls could dramatically improve user experience in slower internet regions.

From a business strategy perspective, authentication directly affects:

  • User acquisition

  • Retention rates

  • Conversion rates

  • Daily active usage

  • Customer satisfaction

  • Market penetration

  • Platform trust

In developing markets, many users are already accustomed to username/password systems because they are faster, simpler, and less dependent on external systems. For many users here, checking email is not as instantaneous or seamless as it may be in more developed markets.

A more flexible authentication system would make Hercules significantly more accessible to users across Africa and other underserved regions, while also positioning the platform competitively against larger global SaaS and AI platforms.

As someone actively deploying, testing, and exposing users to the platform in real-world operational environments, I can confidently say this enhancement would create measurable improvements in adoption and user satisfaction.

I truly appreciate the incredible work your engineering and product teams continue to do, and I hope this feedback contributes meaningfully toward future product evolution.

Thank you again for the support, innovation, and responsiveness.

Best regards,
Mathiang David