We know we have to solve the time zone problem, but unfortunately it’s not as trivial as adjusting everything to the local time zone.
An example: Let’s say the spreadsheet’s time zone is GMT, to make things easy. You submit a form at 7am in San Francisco, so it’ll show up as 2pm in the spreadsheet (SF is at GMT-7). Glide now obviously has to adjust date/times in the sheet back to your timezone, to make the 2pm show up as 7am on your device. Somebody else at GMT builds an app for people attending a conference. The conference takes place in Vienna and the keynote is at 9am. If they put in 9am, somebody in Vienna will see it as 10am, and somebody in SF will see it as 2am, when actually everybody should see 9am, regardless of where they are.
It seems to me that eventually app creators will have to tell Glide which date/times are to be adjusted to local time zones, and which ones are “absolute”. For the time being we chose what we thought would be what causes the least net confusion.
The “App: Logins” sheet was only intended for informational purposes when we introduced it, and we didn’t much consider how its date/times mesh with the ones in the data sheets.
So, apologies for all the trouble. We’re thinking about the problem.