3 ms·
I personally make decisions based on what the project requires rather than some template. Most websites for me are informational, so mobile-first works well. N
by hipsterrific 12y ago
I personally make decisions based on what the project requires rather than some template. Most websites for me are informational, so mobile-first works well. Not a whole lot of functionality to test so we can focus on building the website and make it look on any size device.
However, apps are a different ball game. I'd rather focus on usability, experience, and functionality. I'm not going to try and hobble the app by trying to beat a round peg into a triangle, square, whatever shaped hole. I find that most web applications which have large swathes of functionality benefit from native code, so I usually skip mobile-first design and just do a native app (Xamarin or Titanium works). Why? Because I don't want to sacrifice usability, experience, and functionality. Most apps, I've found out, have different experience, usability, and functionality on difference devices.
- armandososa 12y agoYou can do great mobile experiences on web, but it does require extra time and extra thinking. I don't want to download a new app for every new service I want to try, so I will say that there's still space for really good mobile web apps.
- hipsterrific 12y agoTry and not all web apps should have a mobile web app. But there's are instances where a productivity app will benefit from having a mobile app than just a responsive website. I've worked on a couple of web apps that made mobile-first their paradigm and it sucked. Testing sucked. Dev'ing it sucked. We had to sacrifice a lot on usability and experience which sucked a lot. A mobile app would have made more sense than a responsive site. Then again, I used trulia and having them ask me to download their app was just stupid as the app provided zero value to me (their responsive site was perfectly fine).