110

Voyager might become a native App in the future! (sort of) (lemm.ee)

submitted 3 years ago* (last edited 3 years ago) by fer0n@lemm.ee to c/voyagerapp@lemmy.world

56 comments fedilink hide all child comments

It is a limitation of a PWA. A native app (wrapper) will likely be coming though, and a custom Capacitor plugin could theoretically interface with the native API to switch out icons. Theoretically. No promises though :)

Quoting this comment by the dev

top 50 comments

sorted by: hot top new old

[+] Fluid@aussie.zone 42 points 3 years ago* (last edited 1 year ago)

[deleted]

[-] Cqrd@lemmy.dbzer0.com 31 points 3 years ago* (last edited 3 years ago)

With a capacitor app it can be both a PWA and a native app from the same code base. This wouldn’t take away, only add possible functionality for those who choose to install it natively.

There’s a lot of native functionality that a PWA cannot access, like app icon changing, certain gestures that Apollo took advantage of (tapping on the top to scroll to the top, for one), and some other things that have been requested.

[-] ABeeinSpace@lemmy.world 21 points 3 years ago

I would be so happy if we got Apollo-style scroll to top. That’s the one thing I’ve really been missing

[-] Dark_Arc@lemmy.world 14 points 3 years ago

Well... Part of that is just that web apps have much worse efficiency and performance compared to native apps. That's not to say their performance and efficiency is bad, but a native app will beat a web app everytime. The DOM and JavaScript are just not great models in terms of efficiency and performance.

[-] gunnm@monero.town 8 points 3 years ago

How is your performance with Voyager?

[-] kryllic@programming.dev 6 points 3 years ago

In my opinion, it's been great and feels pretty close to native anyway. Some issues with the screen freezing when trying to scroll after swiping away from a post but other than that, it's super nice. Plus updates are so quick to install, really like that too.

[-] BURN@lemmy.world 4 points 3 years ago

Problematic

I get lots of random freezes, actions not registering, etc

Doesn’t make it unuseable, but it’s not a great experience

[-] gunnm@monero.town 3 points 3 years ago

With all browsers?, here runs fine with chromium.

[-] ryo@lemmy.eco.br 2 points 3 years ago

The main issue is Safari, bugs in webkit bog everything down. And iOS is stuck with it.

[-] BURN@lemmy.world 1 points 3 years ago

No browser as far as I know. I installed the PWA and haven’t touched anything else.

I’m on iOS exclusively with no plans to use a desktop interface

[-] Dark_Arc@lemmy.world 3 points 3 years ago* (last edited 3 years ago)

I think it's acceptable, though I am working on my own ... for now experimental ... Lemmy client in C++/Qt/QML ... maybe eventually for desktop and mobile devices alike :)

[-] gunnm@monero.town 3 points 3 years ago

A desktop client would be a game changer for sure.

[-] TheFrirish@jlai.lu 12 points 3 years ago

imo we need a webapp alternative and voyager is it.

[-] cloudless@feddit.uk 7 points 3 years ago

Many people have not heard of web apps, they do not know how to find or install web apps.

Most of them are more familiar with the app stores. They are more comfortable using what they are familiar with. They might have been using the app store since the original Angry Bird was released.

It is good to have choices.

[-] fer0n@lemm.ee 8 points 3 years ago

Yes, I think even if it’s just a wrapper and nothing else changes other than the app being in the App Store, that’s probably worth it because you’d get more users.

[-] UnanimousStargazer@feddit.nl 4 points 3 years ago

The developers can bring out both.

[-] Pleonasm@programming.dev 4 points 3 years ago* (last edited 3 years ago)

The user experience is nicer as a native app, if done right. With a PWA, you have to deal with anything crappy that the browser inflicts on you, and the developer largely can't do anything about it. For example, Chrome sometimes just crashes or freezes entirely on me, which means Voyager can too.

See elsewhere in this thread for examples of little things that stem solely from being a PWA .

Don't get me wrong, I think Voyager is great for a PWA and it probably gets a lot of value out of being a PWA making it easier for people to contribute. But it's just not as good as native for me.

[-] LazaroFilm@lemmy.world 3 points 3 years ago

Most native apps are still JS in an app. Memmy is React for instance. So WefWef would be offered as both.

[-] gunnm@monero.town 1 points 3 years ago

What makes it better than PWA?

[-] LazaroFilm@lemmy.world 2 points 3 years ago

Some functions are not open to PwA such as tap top of the screen to go back to the top, icon swapping, updates without deleting and re-installing (which deletes all you preferences) and some other iOS API functions.

[-] gunnm@monero.town 6 points 3 years ago

You don't need to delete and reinstall.

[-] LazaroFilm@lemmy.world 0 points 3 years ago

Well if you wan to change the icon you do.

[-] shashi154263@lemmynsfw.com 3 points 3 years ago

My biggest problem with the webapp is that it fills my Chrome history, so it basically becomes useless.

[-] theycallmebeez@lemmy.ml 3 points 3 years ago

ever heard of React Native?

[-] puppy@lemmy.world 19 points 3 years ago

Voyager is perfect as is. Lightning fast to get updates, don't need to be at the mercy of Apple or Google to get into the official stores. And less work for the developers to publish a new version.

As users you don't perceive a difference. A native app in theory could cause your system to be vulnerable if a bug exists.

Because of the above reasons I'd really like Voyager to remain a PWA.

[-] Ilikecheese@lemm.ee 10 points 3 years ago

Voyager is perfect as is.

Except for the scrolling issue on iOS. If they don’t figure out a way to resolve that, I don’t care how many features they keep adding, I’m out. I’ve been tolerating it so far, and everybody keeps hand waving it away with “it’s a limitation of safari” and “all you have to do is not touch the screen for a second and it works like normal”. Uhh…no. This needs to be fixed. Once people have multiple other options, that don’t have this hindrance, (and honestly, I think we’re probably well past that point already) I can’t imagine too many people wanting to use this app vs literally any other choice.

[-] djc0@lemmy.world 3 points 3 years ago

What scrolling issue? The missing top-tap scroll-to-top functionality?

[-] Ilikecheese@lemm.ee 11 points 3 years ago

Every minute or so the app just refuses to scroll at all. The screen freezes up and nothing happens. The only solution is to sit and wait for a second without touching the screen until it decides to work properly again.

It’s borderline unusable, and I can’t fathom how so many people experience it and just tolerate it. I’ve just filed it under “Lemmy as a whole is new and kind of janky and it will eventually improve” but it’s starting to get to the point where it needs to be fixed or people will abandon this app for one that doesn’t have that problem.

[-] djc0@lemmy.world 3 points 3 years ago

Ug that sucks.

For the data point, I don’t have that issue. Not sure what the difference is. I’m using an iPhone 12 mini and iOS updated to the latest. Voyager works really well for me. Remarkably well.

Clearly it’s a problem many are having based on the upvotes. Hope it can be fixed.

[-] bufordt@sh.itjust.works 0 points 3 years ago

So what you're saying is Apple sucks at programming, so you want voyager to make an iOS app?

[-] Ilikecheese@lemm.ee 1 points 3 years ago

I’m didn’t say or imply either part of that, but I guess nice try on trying to put words in my mouth for some odd reason.

[-] Cqrd@lemmy.dbzer0.com 4 points 3 years ago

Capacitor apps can be both.

[-] fer0n@lemm.ee 2 points 3 years ago

I don’t think them making the native app wrapper means the PWA is going away

[-] fer0n@lemm.ee 2 points 3 years ago

Nothing is so perfect that it can’t be complained about. Also, voyager definitely has some (admittedly smaller) annoyances that stem from it being a web app.

[-] puppy@lemmy.world 2 points 3 years ago

annoyances that stem from it being a web app.

Such as?

[-] fer0n@lemm.ee 5 points 3 years ago* (last edited 3 years ago)

scroll-to-top doesn’t work
back swipe is unreliable (works 30% of the time)
after going back you have to wait a second before you can scroll
no app icons packs
no haptics
text select doesn’t work if you immediately go down since it scrolls the page instead

Don’t get me wrong, it’s still impressive. But I‘m very aware that it’s a web app and I have to step carefully. These might be small things, but they’re constantly annoying me.

[-] Untitled_Pribor@kbin.social 1 points 3 years ago

don’t need to be at the mercy of Apple or Google to get into the official stores.

Ipa/apk s exist though, they can just have those on the website and not care about the official stores

[-] kratoz29@lemmy.world 13 points 3 years ago

No promises though :)

REMAIN CALM.

[-] fer0n@lemm.ee 2 points 3 years ago

will likely be coming though

[-] hogart@lemmy.world 10 points 3 years ago* (last edited 3 years ago)

I like that you can develop for both iOS and Android at the same time. And no need to verify every update towards the store.

[-] ikilledlaurapalmer@lemmy.world 6 points 3 years ago

Agree. This is a ridiculously good implementation and I don’t understand why nobody has gotten this right until now. Hallelujah holy shit.

[-] poquito_cabeza@lemmy.world 4 points 3 years ago* (last edited 3 years ago)

Voyager has converted me into a PWA believer.

[-] gunnm@monero.town 8 points 3 years ago* (last edited 3 years ago)

Native as just a wrapper with some extra features I guess.

I see not wrong having both, I think the key of Lemmy's adoption is how easy is to recommend Lemmy by just pointing to an instance with Voyager locally installed as m.lemmy.world.

Voyager should still be developed as PWA.

[-] fluffy@lemm.ee 7 points 3 years ago

Sounds pedantic, but I still wouldn’t call that a “native” app. It’s just a wrapper.

[-] fer0n@lemm.ee 4 points 3 years ago

I agree, that’s what the "sort of" stands for. Depending on how the implementation would look like, it might still make some of the small annoyances that I currently have go away (scroll-to-top, back swipe, scrolling hiccup, multiple app icons, haptics, …).

[-] Zummy@lemmy.world 5 points 3 years ago

Personally, I would like to see a Native App. I get that this PWA makes it easier to develop for both Android and iOS, but there’s something about Native apps that just seem like a better experience to me.