Hey @spspencer! Thanks for the support and the kind words. Let me try to address your issues as best I can. At a high level, we are in the same place you are, and are working on solutions.
Quoted from spspencer:That being said, Scorbit's login interface is the worst I've seen in forever. Right now, I'm seeing two issues.
The first is, Scorbit still hasn't figured out how to keep someone logged in for more than one game. Seriously, this was solved by Netscape Navigator in 1994.
I think by login you mean claim a slot, which is different than a login. The app keeps you logged in indefinitely. The player slots are unclaimed by default because of the tendency for the product to be used in multi-player arcades and the issue of claiming someone else's slot. I think Stern's solution is a very good one, but for security reasons and future features, we have a stronger need for authenticated identity during your experience with the game. Now, this being said, we have developed a solution for this we call Hog Mode (see the previous posts on this topic) that we'll be pushing out in an upcoming release.
Quoted from spspencer:Secondly, when I use the Scorbit app to view one of my local venues, it will automatically assign me to the current game even if I'm not playing. It is very annoying. This past weekend I was at my local arcade and I was trying to show my buddies Scorbit so they would join and log in. As I pulled up the venue and selected the game, it automatedly logged me in as player 1, even though I wasn't playing. I should be able to use the app to see what is going on in the venue without signing in to the currently playing game.
This is because you have it set for auto-claim, which is a feature designed for home users. The irony is your'e describing the problem in a nutshell. At home, with the app unlocked, you can play over and over again, whereas at the arcade, that feature screws everything up.
We are removing the generic "auto-claim" feature and replacing it with Hog Mode soon, I think this will make you happy.
Quoted from spspencer:To go back to my first point, why can't I stay signed in to my home pin? I'm not a programmer, but I can think of tens of ways to do it.
:set current user as past user
:if past user = current user
:set next user = current user
or,
:is user logged in?
:stay logged in
or,
:does only one person log in to machine?
:keep that person logged in until asked to log out
or something like that.
We've spent so much time interviewing operators, home users, players, manufacturers and others about this "duality" of the two use cases and how they present different problems, and I think our solution will work. We shall see! Meanwhile, please turn off auto-claim when you're out and about, and turn it on with the app open when you're home. If auto-save is set, it will also save every score automatically. Once Hog Mode is released, you can leave the same feature on all the time and it will give you the ability to stay claimed for repeat games without too much trouble. It works like a kill-switch, where if you step away for a specific period of time without turning it back on it resets.
Quoted from spspencer:I know you guys are big brotherish from the posts here. "let me check on your game". Seriously, if you see a machine in a home venue where 99/100 of users are the same user, how hard can it be to say "hey this machine is so-and-so's", and leave that user logged in?
Any time Scorbit assumes anything about identity we get in trouble (as you explained earlier about your use in an arcade). It becomes particularly important when you start offering payments and other credit-consuming features into your app, in which case you need to be super careful.
Quoted from spspencer:I don't see the logic about issues with public games, mainly because there are several hoops to jump through to get logged in. A. you have to care enough about pinball to know Scorbit exists. B. You have to care enough about Scorbit to sign in. If you have both A and B, you are smart enough to log out after a game, if you choose to.
People just don't log out. It's the number one complaint the owners/venue operators tell us about Stern's solution, but that's fairly adjustable.
Quoted from spspencer:You are in the hardware and software business. To sell more hardware you have to fix the software issues. Have you considered open sourcing the software?
The community will have persistent log in solved before this weekend. You could probably furlough your janitor for two weeks, send the saving to India, and have the log in issues fixed in a week as well. Hell, I'll give you an if statement today if you need one.
Having said all that, I still love you and want you to succeed. I just don't see how you can't manage single user log in when Stern does it perfectly. I log into insider connected, and I can play as long as I want. It stays logged in until I hold the flipper button for a few seconds to log out. Simple and elegant, and worth paying for.
Haha well I love your optimism about the open source community fixing things over a weekend... It's encouraging to me that it appears that simple, because that is what we want! The truth is that we have a lot of moving parts: the hardware when it's ours, the hardware when it's not (like JJP), the dozens of platform differences between different classic games, the training/adaptability of the code running on the Scorbitrons, the firmware and code that runs on the hardware, the complexity of the distributed network and server infrastructure that has to work in real-time on a global basis, the datastore, the web-based visualizations and tools, and of course, the app itself which has non-player features for operators as well as player features. It's definitely the most complicated service to deliver I've had the pleasure of working on. It has it's puzzles to solve and areas to innovate, but it can also be a beast!
Just FYI, the reason there is few to no open source native mobile apps out there is largely because of the complexity of their design, maintenance, code signing and app store interactions. It doesn't mean it's impossible, it's just really hard to pull off in a clean and fast way. The QA and user testing prior to release and multiple platform tests, privacy/GDPR compliance, CPI, etc., just because hard to integrate with an open source framework. App development sucks, to be honest. However, a necessary evil...
The point is, we all agree... The app has to be simpler and more elegant, and we're working on it.