Meet-upsBeta

A ride with friends, free, up to 25 people. A meet-up is one screen, so you fill it in, press one button, and text the link to your friends.

The form#

The screen is headed Plan a ride with friends / The quick way, fill this out and share the link. You can edit anything later. Nothing you enter is fixed, which means you can send the link while the plan is still loose and fill in the rest as it firms up.

Press Create & share. The meet-up goes live and you get a link to send, and that link is the only thing your friends need in order to open the ride page.

To change a meet-up after you have sent the link, open it and press Edit. The same screen opens with everything you already filled in, so you only touch the field you want to change. The button reads Save changes instead of Create & share.

Saving changes rewrites only the fields you edited, which are the name, the date and time, the place, the description, who can come and the attached routes. The link and its join code are set once when the meet-up is created and are never rewritten, so a link already sitting in a friend's messages still opens the same ride. Answers are held against the rider rather than against the details, which means everyone who already pressed I'm going or Interested stays on the list. That holds for the Fix it change below as well.

Who can come#

If a friend opens the link and cannot get on the ride, check this setting, because an older meet-up can hold a third one, Invite only (old setting). Nobody can join a meet-up on that setting. The Invite panel says so: Nobody can join this ride yet.

Your friend gets no warning of any of this. The link opens the ride page for them with the date, the place and the I'm going and Interested buttons on it, so the ride looks joinable until they press one. The answer is refused at that point and the page reads Could not RSVP. No reason comes with it. Nothing on their screen says the ride is limited to a list, which means from their side the page reads as broken rather than as a setting you can change.

To fix it:

1. Open the meet-up.
2. Press Fix it in the Invite panel.

The setting changes to Friends only, and the date, the routes and the link are unchanged, so the link you already sent starts working. The toast reads Anyone you invite can join now.

When a route does not attach#

A route can fail to attach while the meet-up itself saves, which is why the toast reports both halves at once:

Meet-up saved, but N route(s) could not be added. Open it to retry.

The meet-up is saved and the link works. Only the routes that failed are missing, which means they are not listed in Routes (N) on the ride page. To put them back, open the meet-up, press Edit, select those routes again, then press Save changes.

The ride page#

The host, the riders and anyone holding the link see the same page, so nobody has to be told separately what is on it. Top to bottom, it shows:

• A picture with the meet-up name on it.
• The RSVP buttons.
• When and where, and the count line.
• The description.
• The Invite panel.
• Routes (N), with a map beside it.

The host also sees icons for Share, Edit and Delete, because the host owns the ride. A rider sees no Edit or Delete icon, and on a Friends only meet-up no Share icon either, which means an unlisted ride spreads no further than the host sends it. To bring someone else along, ask the host to send the invite.

RSVP#

The count line reads N going · M interested, so you know how many riders to expect before you set off. With nobody interested, the line reads the going count alone.

The 25 in the line at the top of this page is the size a meet-up is created at, and it is fixed at the moment you press Create & share. Nothing on the ride page reports a full meet-up, so no rider is shown a full message and no host is asked to make room. The count on that line is a tally rather than a limit.

Withdraw appears only after you have answered, because there is nothing to take back before that. Press it and your answer comes off. The count drops by one. Withdrawing changes your answer and nothing else, so the ride page still opens for you with the routes and the map on it. Press I'm going again to rejoin.

RSVP needs you signed in, because your answer is attached to your account. Press I'm going signed out and the toast reads Sign in to RSVP. Nothing is recorded, and the page still shows the ride, the routes and the map. Sign in, then press I'm going.

Invite#

Invite lists your INVIA friends, each name with its own Invite button, so one press sends that friend an invite they see inside INVIA.

For anyone not in that list, press Send a link instead / For anyone not on INVIA. Goes out as a text or an email. Anyone holding the link can open the ride page, so a friend without an INVIA account still sees the plan.

With no friends on INVIA yet, the list is empty. Send a link instead is still there and still works, so you can invite by text or email before anyone joins INVIA.

Routes#

Routes (N) lists the attached routes, and the map beside the list draws every one of them, so a rider can see the ride before agreeing to come.

Send to device needs a Garmin connected first, which means pressing it with none connected brings up the toast Connect a Garmin from the Device page first. Nothing is sent. The route is untouched. Connect a Garmin on the Device page, then press Send to device again.

Send all N is the same button under a different label, so it behaves the same way with no Garmin connected. No route goes across, and the toast reads Connect a Garmin from the Device page first.

When a group does send, the routes go across one at a time, and the first failure stops the run. The routes already on the Garmin stay there and the rest do not go, and the button turns red and reads Retry. Pressing Retry starts the whole group again from the first route rather than picking up where it stopped, so a route that already went across is sent a second time. A route with no map data in it is skipped without a message, and if no route in the group has any, the toast reads These routes have no map data to send.

With no routes attached, the map panel reads No routes yet, which is a prompt rather than a fault. Under that:

• A host reads Add a route and it will be drawn here for everyone you invite.
• A rider reads The host has not added a route yet.

Everything else on the page works: the RSVP buttons, the invite panel and the link.

Riders can submit their own routes, and the host is the one who adds them, so the ride page stays under the host's control. A route a friend hands in is held for the host rather than attached to the ride, so nobody else sees it on the page or the map until the host adds it. The host's panel is headed Routes from your friends (N) and says as much: Nobody sees these until you add them to the ride.

The host presses Add on a route and the toast reads Added to the ride. It stays credited to whoever built it. The route joins Routes (N), the count goes up, and the rider who built it keeps the credit. Declining a route rather than adding it leaves it off the ride page. On the friend's own screen the route reads Waiting until the host acts, then In the event once it is added or Not used once it is declined. The route stays credited to the friend who built it either way.

Deleting a meet-up#

Deleting removes the ride and nothing else, so the routes you attached to it stay in your Library.

1. Press Delete.
2. Read the bar: Delete this meet-up? This can't be undone.
3. Press Yes, delete.

INVIA returns to Events. Then:

• The meet-up is not in your Events list.
• Anyone opening the old link reads Event not found.
• Your routes, rides and collections are untouched. They are still in your Library.

There is no undo, so if you delete a meet-up you still want, make a new one and send the new link.