[CSDude]

Not all things are supposed to be mobile. All the products we write are supposed to run on a large display for our case.

[robbrown451]

I still can't imagine tying yourself to a system that precludes mobile. That seems like a terribly bad idea at this point.

[ethanbond]

For certain applications, you're right that's an awful idea.

For others, it's an equally bad idea to limit your toolbox based on an irrelevant criterion.

[robbrown451]

I question how truly limiting that is. I mean, if you have a framework or library that has the restriction that it won't work well on mobile -- unless there is a really good reason for that restriction -- it seems to me that that framework/library probably isn't ready for prime time and will either gain mobile support, or will soon disappear.

[godDLL]

That might be so, but the rest of the world cares deeply about mobile, even to the point of caring about mobile first. You should get onboard.

[CSDude]

Maybe you should realize not all software are made to be used on 5inch devices, considering Palantir's tools, data exploration and other data intensive sites, it does not make sense to focus on mobile, because your target audience will not use them. Instead of me getting onboard, you should realize generalizing all use cases would not work in real life.

[WhitneyLand]

Respectfully, you are wrong on these points.

1). Mobile is not just about 5" devices. It's also about tablets, and even about working well on larger iOS devices like the iPad Pro 12.9".

2). Data tools can be fantastically useful on mobile when adapted to make best use of the form factor. Lots of the data exploration/analysis tools out there have nice solutions.

3). Your target audience would use them. I'll bet you money it would take less than a day to sketch a few mobile scenarios, based on your own software, that a focus group of your users would rate as "very useful".