![](https://lemmy.world/pictrs/image/00dfeba7-83e1-4813-8b21-4cc4af5868cf.jpeg)
![](https://lemmy.world/pictrs/image/d2e1ce0e-4bc8-48ba-8e8c-e0b6fcef159b.png)
The mobile theme on lemmy.world is Voyager. You can see it linked on the lemmy.world sidebar. Voyager is just a web app, so it can be hosted by instances as a mobile UI.
(iOS | Web | Unity3D) Developer
the more you get, the less you are.
The mobile theme on lemmy.world is Voyager. You can see it linked on the lemmy.world sidebar. Voyager is just a web app, so it can be hosted by instances as a mobile UI.
This is great feedback. Honestly I’ve been primarily focused on integrating features so far. In the next couple of releases I plan to go through and focus on refining the UI making it more readable, reactive, and customizable.
I hadn’t really considered adding a jump button, but I can absolutely look into that as an option. I might even see if I can fit that in the next release, as it should be quite simple to implement.
As for open sourcing, I have not decided just yet. I would prefer open source, but I need to put some more thought into it before I make a decision.
Free, yes. Open Source, not as of now. I just haven’t decided yet if I’ll be open sourcing the project or not.
Thank you! I don’t have a firm release date just yet, though I am pushing for a release date sometime at the end of October. This is largely dependent on how much I can get done in that timeframe, so this could change.
That’s great, glad your liking it so far! I definitely plan on adding a lot more customization options going forward. Right now there is not much in terms of customization, I’ve primarily been focusing on making sure all the core features of Lemmy are supported before transitioning to appearance settings.
Arctic is at a point now where virtually everything except for Admin tools are supported, so I am planning to start adding more customization options, and detail adjustments in the next couple of releases. I try to push at least one update a week with new features and fixes.
I’m always open to suggestions so if you have any feedback, don’t hesitate to ask.
Great question! No information is provided by TestFlight to the developer by joining a test group. When submitting feedback such as crash reports, or screenshots, then only anonymous device information is provided such as iOS version, device type, connection type, time zone, battery level, free disk space, and screen size. Optionally users can also provide their email address when submitting feedback so the developer can contact them, but this is not required.
There are also private TestFlight groups where you need to share your email with the developer so they can specifically add you to the test group, but that is the only difference between private and public groups.
So you can rest easy, you’ve not been sharing any information just by joining a public TestFlight.
Here is a shameless plug for my own Lemmy app Arctic. It’s a fully native pure Swift based app built with performance and content presentation in mind. It’s packed full of features, and more are being added all the time.
More information is available over at !arctic@lemmy.world
You can try my Lemmy app, Arctic. It’s a pure swift based iOS app, written with performance, and content presentation in mind. It’s packed full of features, and new ones are being added constantly.
You can read more about Arctic over at !arctic@lemmy.world
My pleasure. I’m really excited for the next release. I have a bunch of new features, enhancements, and fixes in this release that should make the app as a whole, feel more polished.
Ayyy, thanks for the shoutout! This is the first time seeing Arctic mentioned in the wild.
Thank you!
I implemented collapsible comment chains in v0.2.1 which should be out within the next day or two. I added settings as well to choose between (tap|swipe|both|disabled) for the feature. I’ve been testing it for a few days and it seems to be working great.
I’m also working on a feature to automatically collapse low score chains when opening a post, though that needs some work and likely won’t be included in this next release.
Thanks for the feedback!
Thank you, much appreciated!
Yes, I’ll definitely add that option in. I actually broke a few things with the compact cells while working on some performance optimization yesterday, so I have some work to do on those anyway. I was also planning to add a medium cell option as well.
This will all be included in v0.2.1 which should be out within a couple of days.
Thank you for checking Arctic out, and for the suggestion.
Here is a shameless plug for my own Lemmy app Arctic. It’s not left TestFlight just yet, but it hopefully will soon. It’s a pure Swift based app built with performance and content presentation in mind.
More information is available over at !arctic@lemmy.world
I’m not sure about Avelon specifically, but I am the developer of Arctic and since I’ve seen several posts about this issue in several clients with no developer responses, I thought I would chime in.
Most clients (mine included) rely heavily on opengraph metadata for generating link previews, and presenting in-line content. This includes information like titles, descriptions, direct image/video links, etc. RedGifs serves opengraph data on all of their webpages and this is how (i’d assume) most clients retrieve the video link for displaying the media in-app.
Well recently (in the last few weeks) RedGifs made some changes. They still serve all the same metadata, however the video link they provide will not load unless accessed via their API. Well this is kind of silly, why provide the link if it cannot be used. Anyway, due to these changes, I decided to apply for a client key for their API. They do have some restrictions as to what type of clients can use their API, but Lemmy apps on apple/google storefronts should fit their guidelines. However it has been several weeks since I applied for the API key, and I have received no response. I’m not sure if other clients have had similar issues or not, but I though I’d share my own experience with attempting to resolve this in my client.