Reasons to Consider Building For Web First, Mobile Second
federisgroup.com
Reasons to Consider Building For Web First, Mobile Second
1–7 of 7 posts
Re: Reasons to Consider Building For Web First, Mobile Second
#2My last startup we went mobile first and it sucked. We were bootstrapping so also contracting. The pressure of having to maintain two codebases (in this case iOS and Rails) as well as keep clients happy left a particularly bitter taste. That's before you do any marketing too!!
For my new one I've purposefully chosen something which can be built completely in rails and still be useful. So much easier when dev resource (i.e. me) is constrained.
Re: Reasons to Consider Building For Web First, Mobile Second
#3Mobile first means design your website for mobile devices first, not build a native app first.
Re: Reasons to Consider Building For Web First, Mobile Second
#4Mobile first means design your website for mobile devices first, not build a native app first.
Thank you for posting the correct answer.
Re: Reasons to Consider Building For Web First, Mobile Second
#5[deleted]
Re: Reasons to Consider Building For Web First, Mobile Second
#6Mobile first means design your website for mobile devices first, not build a native app first.
Yes. Good examples are the Bootstrap and Foundation frameworks that are now very much mobile first.
Re: Reasons to Consider Building For Web First, Mobile Second
#7Mobile first means design your website for mobile devices first, not build a native app first.
Instagram is an example of "mobile first" in the sense of the article. It's a thing.