Skip to content

Utility and Loading Screens

Waiting Screens, Sign-In, and Other Everyday Utility Screens

Section titled “Waiting Screens, Sign-In, and Other Everyday Utility Screens”

Understand what the app is doing while it loads, signs you in, or asks you for something small like a location, and what to do when one of those moments takes longer than expected.

  • You need the Velora app installed, or the web link someone shared with you.
  • No account is needed to open the app or to look at a public event. You will be asked for your phone number only when you do something that belongs to you: claiming an invitation, buying a ticket, checking in, or leaving feedback.
  • Have your phone nearby so you can receive the verification code.
  1. Open the app. You see the brand screen with the “plan boldly, connect deeply, share joyfully” animation and a progress bar. In the background the app restores your previous session, checks for a newer version, and works out where you should land. This normally takes a second or two.

  2. Let the app take you to the right place. If you arrived by tapping a shared link - an invitation, an event pass, a ticket purchase, a feedback request - the app carries that link through the loading screen and drops you directly on it, even if you had to sign in on the way. If you opened the app on its own, you land on your last used area: your communities, your events, or vendors.

  3. Enter your phone number when asked. Type the number that can receive a code and continue. A “Sending code…” panel appears while the code is on its way. If the number is not accepted, the field shakes and tells you what to fix.

  4. Enter the verification code. Type the six digits from the message. If the code is wrong, the boxes clear so you can try again; if the message has not arrived, use the resend option. Once you are verified, the app returns you to whatever you were trying to do, not to a generic home screen.

  5. Pick your role if you have more than one. People who are both an attendee and, say, an organizer see a role chooser. Choose Attendee to browse and join events. The app switches to the matching area and colour scheme.

  6. Wait through the short task screens. Some actions show a dedicated waiting screen with a plain label: loading tickets, preparing a feedback form, or tracking a ticket after payment. These screens are meant to be brief and will move you on by themselves - you do not need to tap anything.

  7. Choose a location when a form asks for one. A map opens centred on your current position, with a pin in the middle. Drag the map so the pin sits on the right spot, or search for a place by name, then confirm. The address under the pin updates as you stop moving the map.

  8. Read “Coming soon” screens as a placeholder. If a section is still being built, you get a short message instead of an empty screen. Nothing is broken, and nothing you did caused it.

A screen keeps loading. Waiting screens are designed to give up rather than spin forever - roughly ten seconds for start-up. If one hangs, go back and reopen the app; your progress is not lost. If you arrived from a shared link and land on sign-in instead of the event, open the link again after signing in.

The app feels slow. After your first visit, dashboards and lists show your previously loaded content immediately and refresh quietly in the background, so a thin refresh line at the top is normal. A full spinner appears only when there is nothing saved yet to show. Very long lists and image-heavy event pages are the slowest part of a cold start.

Text or addresses look wrong for my region. The brand tagline on the start-up screen is shown in English regardless of your language setting. Place search in the location picker returns results in India only; for a location elsewhere, drag the map to the spot rather than searching for it. Dates and times follow your device’s clock and time zone.

I am offline or on a weak connection. Content you have already opened is kept on the device and stays readable offline. Anything that needs the network - sending a verification code, buying a ticket, submitting feedback, looking up an address - will fail with a short message and can simply be retried once you have signal. If your ticket does not appear after payment, the app keeps checking for a few minutes and then tells you that the ticket will be delivered to you separately; the payment is not lost.

The map cannot find me. If you decline the location permission, the picker stays on a default area and says the permission was denied. Drag or search to the right place, or allow location access from your device settings and reopen the picker.

No related articles are published for this flow yet.