I just wanted to comment on your "focus on accessibility". At a glance, the app doesn't seem to be accessible from a color contrast standpoint.
I haven't downloaded the app yet, so I can't comment on how well it leverages native accessibility features, but wanted to at least call out the potential color contrast issue since you're using accessibility as a selling point.
It seems there is no way to dismiss the giant prompt of “swipe left or right to navigate the app”, making the main visual extremely unattractive. Have you considered other visual queues for swiping?
Was impressed by the UI and the mentioned features, but when I installed the Android app it asked for permission to manage phone calls without any explanation and denying the permission doesn't allow me to use the app at all. If that permission is really necessary, you should create an intro/onboarding that explains why, not just display permission dialogs at the launch. Really disappointed.
@ianissoawesome We just saw that too - want to be upfront and say that we're not doing anything witht that permission and it must be a bug or human error. Iancu is the co-founder and the Android developer of Aerium, so I'll let him deal with the error.
@iancuio, can you please explain what happens there?
Nonetheless, we will be updating the Android app ASAP to get that permission dialogue out of there.
@ianissoawesome Hello!
Aerium Android DEV here. We are not making uses of, gathering or using anything related to phone calls or contacts in your phone.
We are getting the phone IMEI for AUTH purposes on our backend and as a fellow Android Developer you know that requesting the IMEI is grouped under "READ_PHONE_STATE" permission group. That displays as a requirement to access to your contact list, which I totally agree it's absolutely "brutal" and invasive at a first glance.
Very good point about telling the user about that permission, thanks you for the suggestion.
@iancuio Oh, okay, thanks for the explanation! it really got me worried at first. Have you thought about using UUID or Settings.Secure.ANDROID_ID? It might be better because it doesn't require permission and you can often find chinese budget phones using the same IMEI which may cause you a problem.
@ianissoawesome Yeah, I thought of that. But that changes upon factory reset :( While factory resets might not be that common, the IMEI seemed to be the most consistent option.
We will change that in the next version, to the logged in Google Play ID/email. At the moment I'm adding the explanation screen.
I'd love to be able to experience all pro features, to see how accurate they are, for a certain period of time before I commit to upgrade my plan. Considered that?
@ems_hodge
Hi Emily,
First of all, it's another weather app, I know. 90% of people still use stock weather apps. We know that forecasts can't be accurate when predicting past the next 2-3 days, so we built Aerium around that.
For the past year we've been hard at work to improve the accuracy of our system by combining hyper-local weather data from different sources. We call that ExtremeAccuracy.
Other than that, our RainAlert feature was improved by multiple times because we now rely on a better server infrastructure to deliver the notifications.
I'll be here all day if you guys have any questions or feedback *please do have feedback*.
Thanks,
Raul.
I agree with you 100%. Having to subscribe to something sucks, most of the time. Unfortunately for us, there are ongoing infrastructure costs that we need to consider.
We really appreciate your comment and let me know on Twitter if you need a promo code to try out Aerium Pro.
I just wanted to comment on your "focus on accessibility". At a glance, the app doesn't seem to be accessible from a color contrast standpoint.
I haven't downloaded the app yet, so I can't comment on how well it leverages native accessibility features, but wanted to at least call out the potential color contrast issue since you're using accessibility as a selling point.
Pros:Another weather app!
Cons:Another weather app!