Guitar player here. App looks great, but shame it's only for piano. I used a different app that does pretty much the same thing and really benefited from it, the improvement was noticeable after each session.
If you add guitar support it will be an immediate download for me.
I hear you on the other instruments and guitar request. I tried making a violin app years ago and it was a tiny fraction of the traffic of the piano version which I'm guessing is common theme amongst other developers. That's not an excuse but just the reason I didn't focus on other instruments in the past. Now technically I did slightly support guitar in my app in that you can offset the input of notes in settings which would mean you could use the mic as input and play the guitar as you'd expect while sight reading but the onscreen is still piano. Maybe sometime soon
Tab notation doesn't provide full time signature information, if you're picking up a piece of music which you've never heard played before
In tablature, imagine one string's line shows ---10-----7--8------11----13. How long do you hold each note? Clearly 7 to 8 is quick, but how quick? Sheet music gives you this exact information.
There are some settings where it's good for a guitar player to be able to sight read. If you're playing for random bands, or playing classical, it can be a big help.
I have no idea how Apple prioritise their bug fixing, but it really looks to me like bugs only get fixed when adding new features, if at all.
This is such a trivial big win as well, create a software dev team to focus on the outstanding bugs. Head it with one or two senior developers, make it the first step in onboarding new developers. What a great way to learn, and make a difference.
This is not rocket surgery, and Apple really do have a bad reputation here, even with the muggles.
> This is such a trivial big win as well, create a software dev team to focus on the outstanding bugs. Head it with one or two senior developers, make it the first step in onboarding new developers. What a great way to learn, and make a difference.
Sounds nice on paper. In practice, the seniors assigned to the team will see it as a career dead-end (because fixing bugs doesn't get management attention, but flashy new features do), juniors lack the experience to avoid edge cases or to navigate the project structure, and the seniors/intermediates on the "actual" development team don't have time to waste on reviewing and aiding code of juniors and bugfixes because then they have ownership over that...
I couldn't agree more. However the reason we have a Popcorn option on the microwave is because it makes the difference at the point of sale, not at the point of use. Most people when presented with two devices that essentially do the same thing, but one has more options will chose the one with more options because they have been lead to believe it's better.
Design is so often polluted by marketing. The direction of progress from concept to design to marketing to sale should be one way only.
It used to be a real feature, but so many microwave makers made fake ones that popcorn sellers have been printing “do not use the popcorn button ” on their instructions for a while.
I personally wouldn't go anywhere near sideloading applications that haven't been through Apple's verification processes, or advise anyone in my family to do so.
I also think that it is very hard to argue _against_ allowing sideloading.
These two opinions can co-exist.
Make it optional, make sure the user knows what they are doing, and has acknowledged multiple times that they understand the risks, and that they acknowledge support for any problems at all with the phone will be compromised as a result.
Realistically, 99% of iPhone users don't need to sideload, nor understand what it means, and would be worse off doing it on their phones.
Yeah yeah Apple the big corp walled garden big evil boo. Yes they make mistakes, yes they make a ton of money. But, their stuff works better than anything else on the market for the vast majority of people, and their decisions are almost always thoroughly thought through in favor of the customer experience, accessibility, security and safety.
This is exactly what Android is doing. You get enough warnings before loading an APK file, maybe Apple could make it look even scarier to ensure people don't accidentally do it but ultimately it should be up to the iPhone owner's decision.
If you add guitar support it will be an immediate download for me.