Beta Testing Guide

Important: This is a Personal Project

Before you begin, please understand:

Moterra is currently a personal project created by Aaron Mennitto with help from a few friends. This is not a commercial product backed by a company:

• No legal entity: There is no registered company behind Moterra (yet)
• No formal legal protections: No copyrights, trademarks, or IP registrations are in place
• Informal agreements: The Privacy Policy and Terms of Service are guidelines, not legally binding contracts backed by a corporate entity
• Personal effort: This is a passion project built in spare time
• Beta stage: Everything is experimental and subject to change

Why does this matter?

• You're testing a very early-stage product
• There are no formal legal or financial resources backing this app
• Your feedback is helping shape what might become a real product in the future
• If you have concerns about data privacy or legal protections, please be aware of this informal status

That said, we take your privacy seriously and will handle your data responsibly as described in our Privacy Policy.

What is Moterra?

Moterra is a mobile app designed to track and record your motorcycle rides using GPS. Unlike basic GPS loggers, Moterra prioritizes ride quality over raw data:

What We're Testing

During this beta, we're focused on validating:

Core Functionality

• Ride recording: GPS tracking accuracy, point collection, auto-pause
• GPS quality filtering: Accuracy thresholds, spike detection, jitter suppression
• Background tracking: Foreground service reliability when screen is off
• Data persistence: Local storage (Hive), data integrity, no data loss

Cloud Sync

• Authentication: Email/password and Google OAuth sign-in
• Sync reliability: Upload/download rides, bikes, and settings
• Conflict resolution: Handling edits from multiple devices
• Offline mode: Queuing operations for later sync

User Experience

• Onboarding: First-time user experience, permission flows
• Navigation: Bottom tabs, screen flow, intuitiveness
• Performance: Battery usage, responsiveness, memory efficiency
• UI/UX polish: Visual design, error messages, loading states

Edge Cases

• Poor GPS conditions: Tunnels, urban canyons, weak signals
• Network issues: Intermittent connectivity, offline usage
• Permissions: Location, background location, notifications
• Device compatibility: Different Android versions and devices

Beta Expectations

What Beta Means for You

• Backup important rides: Don't rely solely on Moterra to preserve critical ride data
• Expect the unexpected: Crashes, freezes, and strange behavior may occur
• Be patient: We're a small team working hard to make Moterra great
• Stay engaged: Your feedback drives improvements—please share your thoughts

How to Report Bugs

We've made it easy to report issues directly from the app:

Using the In-App Feedback Feature

1. Open the app and go to Profile (bottom navigation)
2. Tap Send Feedback
3. Choose:
   • Report a Bug (something isn't working)
   • Suggest a Feature (you have an idea)
   • General Feedback (anything else)
4. Your email app will open with a pre-filled template
5. Describe the issue and send

The email will automatically include:

• App version
• Android version
• Device model

What Makes a Good Bug Report

Help us fix issues faster by providing:

1. What happened: Describe the problem clearly
2. Steps to reproduce: How can we make it happen again?
3. Expected behavior: What should have happened?
4. Screenshots: If applicable, attach images (very helpful!)
5. Frequency: Does it happen every time, or occasionally?

What Scenarios to Test

We'd love for you to test as much as possible, but here are priority scenarios:

High Priority Critical

1. Record a real ride: 15-30 minutes, actual motorcycle riding
2. Test background tracking: Lock screen, switch apps, receive calls
3. Check GPS quality: Ride in various conditions (open road, urban, tunnel)
4. Try sync: Create account, sync data, check on another device (if you have one)
5. Test offline mode: Turn off wifi/data, record ride, turn on, sync later
6. Add/edit bikes: Create multiple bikes, associate rides with bikes
7. Delete data: Delete rides, bikes, account—verify everything works

Medium Priority Important

8. Explore mode: View your explored tiles, check for accuracy
9. Settings: Change distance units, theme, screen settings
10. Authentication: Sign out, sign in, test password reset
11. Permissions: Deny location, grant later, test permission flows
12. Edge cases: Pause ride, resume ride, very long rides (1+ hours)

Low Priority Nice to Have

13. UI polish: Look for visual glitches, text overflow, alignment issues
14. Accessibility: Test with large text, dark mode, different screen sizes
15. Stress testing: Record very long rides, accumulate many rides

Privacy and Data

Your Data Belongs to You

• Local first: All data is stored on your device, even without an account
• Optional sync: Cloud sync is entirely optional—use offline if you prefer
• You control it: You can view, edit, export, or delete your data at any time
• No selling: We will NEVER sell your data or use it for advertising

What We Collect

• Account: Email address (for authentication)
• Location: GPS coordinates during active rides (never in background when not recording)
• Ride data: Timestamps, speed, distance (derived from GPS)
• Bike info: Nickname, make/model (optional, user-provided)
• Settings: Units, theme, preferences

See our full Privacy Policy for more details.

Beta Period Duration

The closed beta is expected to last 6-8 weeks (subject to change).

Beta Timeline

• Weeks 1-2: Core functionality, major bug fixes
• Weeks 3-4: Sync reliability, performance tuning, UI polish
• Weeks 5-6: Edge cases, accessibility, final testing
• Weeks 7-8: Pre-launch prep, documentation, open beta (possibly)

We'll keep you updated via email as we progress.

Providing Great Feedback

Your feedback is invaluable. Here's what helps us most:

Bug Reports

• Detailed steps to reproduce
• Screenshots or screen recordings
• Device and Android version
• Frequency (always, sometimes, once)

Feature Requests

• Why you want the feature (your use case)
• What problem it solves
• How you imagine it working

General Feedback

• What you love about the app
• What frustrates you
• What feels confusing or unintuitive
• Comparisons to other apps (what they do well)

Be Honest

We want your authentic experience:

• Don't hold back: If something sucks, tell us
• Be specific: "The map is slow" is less helpful than "The map lags when zooming with 100+ points"
• Be constructive: Suggest improvements when possible
• Be kind: We're humans working hard to make this great

Contact and Support

How to Reach Us

• In-app feedback: Profile > Send Feedback (preferred)
• Email: beta@moterra.app
• Response time: We aim to respond within 24-48 hours

What to Expect

• Bug reports: We'll acknowledge receipt and may ask follow-up questions
• Feature requests: We'll consider all requests, but can't implement everything
• General questions: We're happy to help with any issues