Designing for the operating system is actually a form of designing for the user. I believe you should start with standard conventional interfaces wherever you can. Then look for the pain points. What is more difficult in general or in yours specific use case. From there try to build upon the convention and improve it. Sometimes a small tweak can go a long way and other times a larger one is necessary.
Yes, longterm usage efficiency should be considered but perhaps even more important is the efficiency for beginners and casual users. This is why “pro” and “consumer” apps exist.
Snapchat is not a good example. It is the exception. In fact, it was born out of a desire to make it difficult to figure out so that parents and teachers couldn't spy on you. If every app you downloaded had as steep of a learning curve as Snapchat then the app stores would die as people would give up on apps. I truly fear a day where everybody is trying to copy Snapchat. It is unique and it should stay that way. Not every app should attempt to reinvent the wheel.
Yes, longterm usage efficiency should be considered but perhaps even more important is the efficiency for beginners and casual users. This is why “pro” and “consumer” apps exist.
Snapchat is not a good example. It is the exception. In fact, it was born out of a desire to make it difficult to figure out so that parents and teachers couldn't spy on you. If every app you downloaded had as steep of a learning curve as Snapchat then the app stores would die as people would give up on apps. I truly fear a day where everybody is trying to copy Snapchat. It is unique and it should stay that way. Not every app should attempt to reinvent the wheel.