What you can test
Account and onboarding
Try normal signup, login and profile flows and tell us where instructions, verification or navigation are unclear.
Rider experience
Explore pickup and destination entry, scheduling, ride options and local-availability messaging. Do not rely on a ride until the app shows suitable current availability.
Driver experience
Explore driver onboarding and marketplace screens. Actual driving requires all applicable legal, licensing, insurance and platform requirements.
Services experience
Where the GetService customer/service-seeker mode is available in GetRide, explore discovery and request flows and report usability problems without submitting sensitive information.
How to report a useful bug
- Your device type and operating-system version.
- The GetRide app version if visible.
- The feature or screen you were using.
- Short steps that reproduce the problem.
- What you expected and what happened instead.
- A screenshot only if it contains no password, OTP, payment information or other sensitive personal data.
Why this matters
GetRide's current growth stage is about building credibility and improving the software with real-world use while driver and partner supply is developed market by market. Feedback helps the team prioritize defects before larger local launches.
Frequently asked questions
Does testing GetRide mean rides are available near me?
No. App availability and local driver availability are different. Check the app for current local options and do not depend on a ride that has not been confirmed.
Can I send account passwords or verification codes when reporting a bug?
No. Never send passwords, OTP codes, card details or other authentication secrets. Describe the issue without exposing private credentials.
Who develops GetRide?
GetRide is developed by GetService Technologies Inc., the software company behind the GetRide and GetService ecosystem.
Product feedback may be used to diagnose and improve the software. Do not include unnecessary personal or sensitive information.