I believe this is fixed now. It was due to changing the listing type from subscribed to all, when viewing a community feed you are not subscribed to. The behavior is still the same, but it will only affect that one feed, and not change the global setting.

This is fixed now, it was actually caused by the same issue preventing community sidebars from loading correctly.

Alright, I have this fixed now. It was a simple mistake of trying to load the community information, before the community id was set.

Alright, I was able to reproduce this issue. It looks like it is working correctly if you open the sidebar from an open post, but not from the community feed. I’m wondering if this is the same issue that is causing the post composer not to detect the open community.

This should probably be a simple fix, I’ll look into it here in a little while when I get home.

That is exactly how it is supposed to work, It looks like this is a bug. I must have broke this in one of the recent releases. I’ll have a look, it should be a simple fix.

When viewing a community feed, or post, the sidebar will show the community sidebar. If your viewing the home feed, the sidebar shows the instance sidebar. Is this not working correctly for you?

Do you by chance ever use guest mode? I believe switching to guest mode is the only case where the filtering will revert to all. Actually it may also change to all when viewing a community you are not subscribed to, but it should revert back after leaving it.

I’ll have a look at it though and see if I can’t track down what is happening. Thanks for letting me know.

I’m working on this right now, I’ll let you know how it goes.

[Edit]: This is fixed now. The status bar will be hidden with the navigation bar.

Thanks for taking the time to test it out, and provide feedback! It’s always great to have a designer look at Arctic.

• Subscribing to a community can be accessed from the (…) menu on any post, or community feed. (…) -> Community -> (un)subscribe. When searching for a community, you can also use a side swipe to (un)subscribe
• It is definitely time I work on some more icons, it has been a while since I added any new ones. All the icons are made by me, and I am not any kind of graphic designer. My plan for this was actually to run a month icon competition for new icons.
• Padding above posts, are you referring to spacing between posts, or the actual padding between the top of the post cell, and the title?
• Bar highlights? Im not sure I follow what you mean here. The bar shadows(delimiter) due just that, unless I am misunderstanding.
• Indeed, the profile header needs some love. I actually redesigned it recently, and it is an improvement over what it was, but still not what I want.
• Honestly, now that you mention it, I think I should probably replace the Edit / Send button with a Submit button for consistency.
• Opening the post options while scrolling has happened to me a couple of times, but I haven’t found it to be a consistent issue. I can look into it.
• I just added an option to disable Guest Mode in the Account Switcher, it will still be accessible from the Account section in settings.
• I’ve had one other request for a compact subscription list. The reason I opted for splitting into 2 labels is because the community name and community handle are not always the same. I’m going to work on adding a compact layout for this though.
• Which image transitions are you referring to? I believe most images are displayed without an animated transition, but there are a few exceptions.
• Scrolling performance is still being worked on. Since the Lemmy API does not provide enough metadata to determine the final display size of content, additional network requests are needed to determine the size. I’m working on improving this to minimize the hitches while scrolling.
• You are right about the loading state, I need to update this behavior.
• I’ll add an option for hiding the status bar with the top bar. I tried this before, but I was unable to get it working. I’ll look into it again.
• Hmm, I hadn’t noticed the issue with white accent color before, Im not quite sure how I’ll handle this yet, but I’ll look into it. I definitely don’t want to add another theme color just for switches.

Disabling the splash screen on first launch is not possible. This is not set on a timer or anything. iOS automatically manages this, and hides it as soon as the main view is loaded. Without this in place you’d be looking at a black screen while the app loads. I can look into improving the launch time though, this would minimize the display of the splash screen.

I am planning account specific settings, but I have not figured out how I would like to manage this yet. Arctic has a lot of settings, and I don’t want to make things tedious by making each account adopt its own settings. I’d rather like to add a way to override specific settings for individual accounts. I’m just struggling to figure out how to implement the user interface for this.

The name Arctic comes from lemmings. The lemmings natural habitat is typically the arctic tundra. I wouldn’t say that the name Arctic has inspired much in terms of design choices. Though i would love to find ways to incorporate this into the design for stronger branding.

I will say the iPad version is still needing a lot of work. It’s not full of bugs or anything like that, but I haven’t made great use of the larger screen space. I’m still in the planning stages of redesigning this. I’d like to take better advantage of the screen space, and have the layout update dependent on context.

Anyway, thanks for all the feedback. This has given me a lot to work on!

This is coming. I took week off after this last update just because I needed it. I’ve been working on a small updated, mostly just patching some minor issues in the last release. I planned to release this to TestFlight last weekend, and the AppStore this week, however I’ve been fighting a cold all week and it set me back.

I should hopefully release the update this weekend, and I may just submit it to the AppStore as well since there are no braking changes in this release.

I know the AppStore version is way behind, I need to start updating that after each TestFlight release.

Thanks for letting me know, it’s fixed now. There was a formatting issue with that link. By the way, you can also access the GitHub link from the bottom of the settings page.

Currently there is not an option for disabling haptics. I have been planning to go through and add haptics in more places throughout the app, and add some options for configuring the haptics, but I have not gotten around to it just yet. This is something I’ll definitely work on for the next update. You’re absolutely right that it can be an annoyance when a server is having issues, as it can spam errors during that time.

There is not currently a setting for hiding community icons in the subscriptions list. It would be easy enough to add an option for disabling the icons though. My thinking was that the icons were essential since there can be multiple communities with the same name, often times the icon is what sets them apart.

Is this just a visual/aesthetic preference for you, or is there another reason you’d like to disable the icons?

Thank you! I’m glad you’re liking the update.

As for theme contrast and legibility, the default Dark and Black themes should have plenty of contrast, as they are the default dark mode colors for iOS. The rest of the themes are based off of existing code editor themes, which I may need to tweak a little. In the mean time, you can long-press any default theme and duplicate it, from there you can edit any color you want to change, or you can design your own theme from scratch if you’d like.

This is the first beta release of theming support, there is still a lot that I plan to add and update. I’ll need to spend some more time refining the default themes, as most of them were quickly made while testing the theme editor.

My pleasure! Theme support is something I have wanted to add for a very long time, but I never had the time to work on it, as I knew it would be a lot of work. I’m glad you like it. I could be mistaken, but I believe you may be the first person I had spoken to about theme support nearly a year ago, well its finally here now.

I am planning to make some improvements to the theme editor. I want to add descriptions for each color to specify what it changes. I also need to go through and prevent setting transparency for some colors, and I need to add more preview views so you can see how the theme will look in different contexts.

While I was making the default themes, I used vscodethemes.com as a reference for most of them. I just used a color picker and dragged the hex color into Arctic (you can drag and drop any of the colors, including dragging colors from other apps). For testing, you can set the theme you are editing as the active theme, and then whenever you press Save, the theme will be applied throughout the app. This way you can make changes, and then quickly test them in different views.

The themes look great, and the links work well. I didn’t test this until now, but I was able to download and install the themes without leaving the app. So that is great. By the way, if you long press a theme in the theme browser, it allows you to share the generated preview image like the ones I included in the post. I thought this may be useful for anyone sharing a theme to be able to include a preview.

Unfortunately, Apple does not offer a way to enable in app purchases in TestFlight. You are able to switch between the AppStore version and TestFlight version without losing any settings. Alternatively, I do have a Buy Me A Coffee set up if you’d rather use that. I have a link for this in the community sidebar, but I am unable to include alternative payments inside the app itself.

My pleasure, Hope you enjoy it!

Thank you! I was an avid user of Apollo since day one, Arctic was my way of coping with the loss.

This is a great idea, I hadn’t thought about that before. I’ll look into adding this in the next update.

I’m glad you like it!

Thank you for bringing this up, It’s something I keep forgetting to address. Instance blocking in Arctic was added before Lemmy added support for instance blocking. Currently, Arctic does instance blocking locally, rather than using the API. I’ll add support for this in the next update.

Thank you for letting me know about this. I had fixed this before, but I must have broke it again in the last update. I have this resolved now. I’ll have small update out soon to address this and a few other issues.

In the mean time, there is an option in the appearance section “Show Community On Top” which will move the community label to the top of the post. This will prevent this issue from happening until I release the next update.