I just have a list of movies I want to watch. Then my wife can pick any movie from that list and it will be pre-approved.
I made a mobile app for my significant other and she won't use it
231–240 of 310 posts
Re: I made a mobile app for my significant other and she won't use it
#232Not gonna make an account with a password that requires this and that
I’d recommend a password manager
Re: I made a mobile app for my significant other and she won't use it
#233A web app would have solved most, if not all, of these problems.
I'm curious, what do you want to give the author with this comment? Do you think that this is constructive or helpful for what is shared here?
That the web is the better platform for solving his problem and doesn't suffer from the monopoly.
Yes, I think that's constructive. I don't say that what he's done is bad, but have a suggestion how he could have saved some trouble. Why the negative sentiment?
Re: I made a mobile app for my significant other and she won't use it
#234Earlier quoted context omitted.
I don't think comparing Google (Play Store) and Apple (App store) really compare here. Google does let you just publish your app, Apple doesn't 1. The author could have offered an .apk outside the play store. Yes, friends would have had to enable side loading so that sucks but once enabled it's trivial to install .apks. This is no different than MacOS or Windows at some level. No similar option exist on iOS 2. The au…
> The author could have used Progressive Web Apps and just skipped the store entirely on Android and send friends a link. Again, no similar option really exists on iOS. I don't understand this. iOS has a browser, you can use web apps.
iOS has a crippled browser which purposefully does not support PWAs, with notifications and such.
Re: I made a mobile app for my significant other and she won't use it
#235Earlier quoted context omitted.
Why make it an app at all. A webpage wouldn't have to deal with the play store, and when a bunch of friends gather they wouldn't have to wait for people to install it.
If only they could make the WebPage or WebApp installing on Home Screen as easy as pressing a link. ( Which has all sort of other implications ) Otherwise modern day Web Browsing on Smartphone is mentally incompatible with Apps usage.
If you visit a Progressive Web App a couple of times, the browser may ask if you want to add it to the Home Screen. Works for me on Android at least.
Re: I made a mobile app for my significant other and she won't use it
#236Earlier quoted context omitted.
> The author could have used Progressive Web Apps and just skipped the store entirely on Android and send friends a link. Again, no similar option really exists on iOS. I don't understand this. iOS has a browser, you can use web apps.
iOS has a crippled browser which purposefully does not support PWAs, with notifications and such.
iOS does support PWA. Notifications are not supported, but PWA is more than notifications.
Re: I made a mobile app for my significant other and she won't use it
#237Earlier quoted context omitted.
Interesting, since the advice I (a non parent) had always heard was back only: https://www.lullabytrust.org.uk/safer-sleep-advice/sleeping-...
This advice seems to cycle. With our first born we also had to alternate positions. Now with the second we got the strict instructions to let sleep on the back only. According to the help it was because every once in a while the number of babies that die in the crib surges and then everyone has to sleep on their back again. But they don’t really know what is going on.
Back only sleeping has been the recommendation of medical authorities in most of the world for close to 30 years.
It’s not a recommendation that changes every few years.
Re: I made a mobile app for my significant other and she won't use it
#238Why does an app like this need to have a sign-up process with email, username and password? It’s enough for me to not try the app because of the mental overhead and risks involved, but it also seems like a bunch of additional development for no (or maybe negative) benefit.
> Why does an app like this need to have a sign-up process with email, username and password?
In my experience, this almost always happens when a web developer makes a native application. They ignore the platform conventions and interface guidelines and design it as if it’s a web application instead of designing a native application. So there’s a sign-up process because that’s the way it’s normally done for web applications.
The relevant part of Apple’s Human Interface Guidelines:
> Delay sign-in as long as possible. People often abandon apps when they're forced to sign in before doing anything useful. Give them a chance to fall in love with your app before making a commitment to it.
— https://developer.apple.com/design/human-interface-guideline...
Please, if you’re building a native application, actually build a native application not a web application. Native applications run in different contexts with different constraints, you can’t just assume that what works well or is necessary for a web application makes sense for a native application. In particular, dumping new users into a registration screen just because you want to persist state is bad design for most native applications. Native applications don’t need that in the same way web applications do.
Re: I made a mobile app for my significant other and she won't use it
#239> Eat my butt, Apple. Eat my butt, Google. Just let me publish my frickin app, you already emptied my pockets. I feel this. A few years ago, I made a joke app[1] which got a bit famous on campus back when I was in school, and the process of getting it on the Play store was literally harder than writing the darn thing. Nowadays, it even got removed from the Play store for some reason. I couldn't imagine running an app…
As a user, I'm very happy the stores impose stringent rules. "And there are all these stupid requirements. I need at least X screenshots, and they have to be this exact resolution blah blah blah. On top of that, it took so long to get approved. My ADHD brain really suffered waiting for the gratification." I would hate to browse a store where the products didn't have at least X screenshots with at least X resolution,…
I think you misunderstood what the poster wrote. The complaint was:
> and they have to be this exact resolution
And your comment was:
> screenshots with at least X resolution
The problem isn't that Apple forces you to have a high quality screenshot, they require a handful of very specific pixel dimensions, don't tell you what device that corresponds to, so you have to spend way to much time trying to make screen shots on different devices with the simulator and it's annoying, especially if you don't do it often.
Also, they don't actually check if the screenshot is a real screenshot or of good quality. One time I just gave up and resized the screenshots to the required pixel dimensions and they accepted it.
Re: I made a mobile app for my significant other and she won't use it
#240Earlier quoted context omitted.
> The sign up process is just to store your likes so that you don't need to swipe again on the same movies. > Its also so that you can lookup and add your friends. Right, but what about that requires me to type in three magic strings into three (wait, actually probably six?) input fields? Just associate the data on the server with some UUID that you store on my device. Inviting others could work by just sharing a lin…
I like the idea. However I think there is a reason why it typically works like this app does. Now what happens if you switch phones or use multiple devices? The behaviour would be inconsistent. What if I build up a large amount of likes/dislikes? Would they be suddenly gone without way to export them? Additionally, I actually would like it not to store data. Maybe I want to get the recommendation for a movie next tim…
> Now what happens if you switch phones or use multiple devices? The behaviour would be inconsistent. What if I build up a large amount of likes/dislikes? Would they be suddenly gone without way to export them?
I agree this is a likely reason, but I think it’s a cargo cult design that makes sense on the web, but is the wrong priorities for a trivial/frivolous mobile app like this.
I don’t know anything about Android, but with iOS this just isn’t an issue. Everything is backed up and when I get a new phone everything is restored automatically.
Even for the quite uncommon case where a poweruser is switching between iOS and Android, it’s not worth blocking the 99% users who just want to try the app as effortlessly as possible and will never end up in that situation. It would certainly be possible to convert an automatic anonymous user account to one that uses password-based login, for users who care a lot about the data in the app.