Good questions.
Clear answers.

PEV Ride Computer is currently in testing for Android. Coming to Google Play. This website is public so you can learn about the app and its features before release. There is no public store download link yet.

Yes—an iOS version is planned after the Android app is approved and commercially available. We have not announced an iOS release date. The current screenshots, videos and setup instructions cover the Android build; iOS details will be added here as that version takes shape.

Your personal ride library and Garage are stored on your phone. Personal recording, History and replay creation need no account, and your ride history is not automatically uploaded to a Neuralis ride cloud. The app has no ads or embedded analytics service. Personal replay videos are rendered on your phone.

Sharing is optional: group rides, configured safety texts, exports and backups have specific recipients or destinations. You can enjoy the core personal ride tools without setting up group sharing. The website's ordinary hosting requests are separate from the app's local ride library. See how privacy comes first and the Privacy Policy.

Garage includes electric skateboards, electric unicycles, self-balancing boards, scooters, e-bikes, e-motos and custom PEV setups. The app records the ride using your phone. Choose the type and specifications that match your equipment.

No. Vehicle specifications and battery readings are entered by you. The app does not provide live controller telemetry or change controller settings. Range and energy estimates depend on your inputs and conditions such as hills, wind, load, temperature and battery health. Keep a practical reserve.

Not for personal recording, Garage, History or personal replays. Optional group rides use your own Tailscale account and an external sign-in flow. Spotify is optional and separate. There is no PEV ride-cloud account.

Website contributor accounts and community uploads are not open yet. They are separate from app use and will have their own sign-up information if introduced.

Personal GPS recording and installed offline maps can work without an active data connection, subject to your phone's location reception and settings. Download maps in advance. Group coordination needs network connectivity; it is not an offline peer-to-peer radio feature. Safety SMS needs compatible carrier service. Internet access is also needed for external account sign-in and services such as Spotify.

The Android test build uses your own Tailscale account, a supported 64-bit Android device and network connectivity. Provider account, sharing permissions and plan limits apply. iOS group requirements have not been announced.

A recording saves your own ride on your phone. A group shares current riding information with admitted members. You can do either one, or both. Joining a group does not start a personal recording.

The finish sheet lets you choose Save my recording, Leave group, or both. Hosts can explicitly choose End group for everyone; it is not preselected just because they finish their own recording. An activity you do not choose to finish stays active. Read the result before closing the sheet: saving and group departure can succeed independently.

Choose Full map for more room around your position and route, with compact ride statistics and quick Ride, Group and Rally controls. Exit returns to the compact view. Follow keeps your position in view while preserving your chosen zoom and bearing. Panning or focusing on a rally lets you inspect that view; choose Resume follow when you want the map to follow you again. Set up and adjust the screen while stopped.

Admitted members receive your rider name and marker, shared position with accuracy and freshness information, speed, phone battery and participation status. The group also sees its published route, rally information, named responses and attendance, active SOS/all-clear information, any optional SOS message you send and any shared Spotify Jam invitation.

A pending join request does not exchange rider locations with the group before admission. Phone battery is separate from your vehicle's battery estimate. The current app does not save other members' ride tracks or create multi-rider replay videos.

No. Pause affects personal ride statistics and segment handling; location acquisition can continue. Group sharing continues until you leave or the session ends. In the finish sheet, select saving your recording and leaving the group if you want both activities to end. Saving alone does not stop group sharing. Hosts must explicitly choose to end the group for everyone.

An active rally is highlighted in orange; a current arrival is shown in green. The roster distinguishes riders at the rally, on their way, without a response and those who have left. The host estimates arrival from fresh, accurate shared positions that remain nearby and slow for 30 seconds. You can also choose I'm here or Undo my arrival.

Check the age and connection status alongside attendance. Stale location information is not counted as current automatic presence, and missing updates do not prove someone has left. Manual confirmation can remain current while that rider's connection is fresh. Moving the rally resets attendance. Arrival estimates are not proof of safety or exact venue attendance; controls depend on the host supporting this feature.

Tap SOS · 3 taps three times within four seconds, then review the confirmation and choose Send SOS. You can send without typing or add a message of up to 160 characters. While your SOS is active, use Add SOS message or Edit SOS message to explain what you need without creating another incident. Older hosts may support SOS without messages.

Manual Group SOS alerts the admitted group. It does not text your emergency contacts or call emergency services. Three taps open the confirmation; they do not send by themselves. Leaving the screen or app, cancelling, or letting the tap sequence expire means starting again. All clear remains a separate deliberate action.

Incoming SOS uses a repeating double pulse; a rally uses a gentler single pulse. Silence or dismissing the notification stops that alert on your phone. Neither tells the group that you are responding. I'm coming for SOS or On my way for a rally silences locally and sends your response; check whether that response is pending or failed.

An updated SOS message can alert you again if you only silenced or dismissed the previous version. Riders already responding stay quiet while seeing the update. Android notification settings, volume, Do Not Disturb, calls and audio routing affect what you hear. Your own crash countdown takes priority over group sounds. Use Group alert sounds to check readiness and try a short local sound test; a test does not create an SOS or rally.

Yes. The host can review a saved personal ride and publish it as the group's planned route. The shared plan contains its route geometry and name, not the original recording's timestamps, battery readings or event history. The full route can still expose sensitive start and end locations. Review it before publishing. Deleting the original ride does not retract a route already published to the group.

No. A displayed route or rally point helps the group coordinate; it is not turn-by-turn guidance or a guarantee that a path is accessible, lawful or safe. Map data can be incomplete or out of date.

A host can share a Spotify Jam invitation for members to open in Spotify. Spotify controls eligibility, playback and its own session. PEV Ride Computer does not stream or synchronize Spotify audio, and ending a PEV group does not end a Spotify Jam. Spotify music is not included in exported replay videos.

The host starts a Jam in Spotify, shares its invitation to PEV Ride Computer and confirms it there. Riders use Join / reopen Jam to open that shared invitation. Invitation shared means the link is available; it does not confirm that everyone has joined or that playback is in sync. If music is out of step, open Music out of step? and check the Jam in Spotify. Playing the same playlist separately does not join it.

The finish sheet can offer to open Spotify afterward. Leave or end the Jam in Spotify itself; PEV cannot verify that action.

Open History → a saved ride → Replay → Your ride story. Give the video its own title, review suggested stops, add a stop manually and choose the moments to include. Suggested stops cover supported stationary stays of five minutes or more and qualifying recording pauses. Missing GPS remains a gap. Installed offline maps can offer nearby place names as suggestions; choosing one does not establish that you visited it.

Add up to 12 photos per ride, place them along the recorded route or at a stop, and add captions. A reliable capture time can suggest placement; check it and correct it when needed. Photos with an uncertain time need you to choose a place. The app keeps optimized private copies and leaves your originals unchanged. Excluding a photo keeps its copy for later editing; removing it deletes that app copy.

Edits are saved for future exports. Create a new video after changing the title, stops, photos or event choices; an existing exported video does not change.

In Replay range, choose Trim ride, move the start and finish handles and review the selected route. The times refer to the original recording. Choose Apply range to use that section in the preview and next video; its displayed statistics describe the selected section. To restore the full selection, choose Reset to full ride, then Apply range.

Smooth Stops shortens sustained waiting in the replay while keeping included stops and photos visible. It starts on for newly configured replays; existing saved edits retain their previous pacing. It does not fill GPS gaps or change your original recording.

Trimming changes the replay presentation, not the saved ride or a full backup. Photos and approved events outside the range are kept so you can expand it again. Create a fresh video after changing the range or pacing, and review the finished file before sharing. Trimming is a manual choice, not automatic protection for home or work locations.

Elevation and hill highlights are estimates from available phone measurements. The app checks GPS and pressure elevation, when available, for inconsistent changes, but some sensor errors can still resemble terrain. Reopen a saved ride to use the current analysis and regenerate a replay if you want that analysis in a new video. Previously exported files do not change. See Support if a hill or elevation total still looks wrong.

Yes, from a supported local music file you select on your phone. Choose material you have permission to use and publish. Importing a song does not grant a license to share it in a video.

There is no Neuralis cloud copy of your personal ride library. Your choices can still send information elsewhere: group sharing, safety SMS, map downloads, file exports, external services and support requests each have their own data flow. A cloud drive you choose for a backup will receive that backup. Read the Privacy Policy for the details.

Only if you keep them private. Ride files and videos can reveal exact locations, including home or work, and selected replay photos or captions can reveal more. A full backup includes saved replay edits and photo copies, including excluded photos still attached to a ride, as well as safety contacts and message history. It is not password protected by the app. Review files before sharing. The current app does not automatically trim private start and end locations.

Save a full backup, copy it privately and restore it on the new phone. It carries saved replay titles, stop edits, photo copies, event choices, replay ranges and Smooth Stops settings with your personal library. There is no automatic ride-cloud sync. Download maps again, keep original photos, music and exported videos separately, review permissions and Ride safety, and set up group sign-in and pairing again. Older app versions may not support newer replay settings or photo-containing backups; keep a backup from before changing test builds.

The app does not call emergency services or arrange rescue. Optional possible-incident detection is experimental and can fail or trigger falsely. When enabled and ready, its countdown can request alerts through the available channels. Delivery and a human response are not guaranteed. Keep another way to request help and read Ride safety support.

Download a PEV vehicle configuration file and open it with Garage → Import vehicle from JSON. Review the preview, check the model and units against your own vehicle, then add it. A configuration file records specifications; it is not firmware, a controller preset or a manufacturer safety approval.

Community uploads are not open yet. See the Community contribution guidelines for the standards being prepared. Downloadable reference material and future user contributions are separate from your private app library.

Start with Your first ride or Support. Email support@neuralisai.com with your app version, phone model and a short description. You do not need to send your full ride history or backup.