revs

joined 2 years ago
[–] revs@feddit.uk 8 points 2 years ago (1 children)

Typical timing as I’d just disabled the swipes as they kept interfering!

Awesome work

[–] revs@feddit.uk 1 points 2 years ago

Hopefully this becomes standard. Looks like Apple were looking into it too

https://www.phonearena.com/news/patent-improves-typing-on-iphone-in-rain_id141115

[–] revs@feddit.uk 9 points 2 years ago

All Apple devices run variants of the same software, so of course they have a consistent UI.

It’s a desktop OS, the same as Windows and Linux.

I’m not sure what you expected, can you elaborate?

[–] revs@feddit.uk 13 points 2 years ago

I’ve started to upgrade when iOS updates stop. As the cost of devices goes up, I just keep them longer so the cost per year is about the same.

[–] revs@feddit.uk 5 points 2 years ago

I have the original SE, it’s still amazing. I do kinda wish I had the AOD though.

[–] revs@feddit.uk 6 points 2 years ago (1 children)

It’s already on the App Store. That’s what this post was about.

Apple are a lot quicker at approvals nowadays, they automated a lot of checks a few years ago.

[–] revs@feddit.uk 4 points 2 years ago (8 children)

iOS issue. Not one the dev can control.

However if you use the TestFlight native app, you won’t get this issue.

[–] revs@feddit.uk 5 points 2 years ago* (last edited 2 years ago) (2 children)

I’ve opened a issue on GitHub to have this added.

https://github.com/aeharding/voyager/issues/553

[–] revs@feddit.uk 2 points 2 years ago

Oh I own that, but haven’t used it in years. I’ll give it another go

[–] revs@feddit.uk 4 points 2 years ago (2 children)

I’ve been using Wipr, but the cookie notice blocking is breaking quite a few sites now

[–] revs@feddit.uk 21 points 2 years ago (1 children)

As others have pointed out:

  1. It’s still pretty early. Many devs might not be very far along.
  2. There aren’t many locations. You have to travel to California, London, etc
[–] revs@feddit.uk 7 points 2 years ago (2 children)

It’s an iOS issue with web apps, not something specific to Voyager.

However if you use the native Voyager app, the issue is fixed

view more: ‹ prev next ›