Jquery mobile is broken

A while back we produced our first “mobile specific” web app, which was produced with Jquery Mobile. This framework seems to make building forms etc so easy for mobile. But after we did a bit of testing on some mobile devices, we soon realized this pretty ui is not without issues. We have various input controls that would simply refuse to work correctly, and even had a date picker control that would… somehow?… actually crash the browser. After a lot of headache and retesting, and removing anything beyond just the most basic of input controls, we finally got things working well enough to release it.

But now I’m finding that, not only was our experience no uncommon, it seems that many others have not done the testing we did and discover the bugs… and have actually deployed production websites using JQM… that simply do not work. I first noticed this with a popular ecommerce package that released mobile extensions- browsing certain pages just simply did not work. So customers who had deployed this option would actually see their mobile sales drop a bunch, instead of improve them as they should. I’ve even seen some analysis that “mobile traffic is junk”, which I’m not convinced is derived from some similiar issues to this.

And just in the last two weeks, I’ve personally encountered 2 other production sites that are having serious mobile website issues that make them unusable to many mobile users.

Is Jquery Mobile doing more harm than good?

Twitter Bootstrap MVC4

Been using the Twitter Boostrap framework on a few MVC web applications lately and have enjoyed working with it. Recently was looking at the next app to be developed and had the idea that using the scaffolding features of MVC with bootstrap themeing would be cool. Wonder if it exists anywhere. 

After a little looking, it appears that it does: http://lostechies.com/erichexter/2012/11/20/twitter-bootstrap-mvc4-the-template-nuget-package-for-asp-net-mvc4-projects/

I haven’t tried it yet but will be soon and will report back here. 

The strange part about this project is that it is listed on the nuget.org website, but I can’t seem to find it inside the package manager utility inside visual studio. 

ip67 android phone

Samsung is releasing a ruggedized version of their latest Android based phone called the Galaxy S4 Active. It is being marketed to the “active” crowd, and the ip67 rating means it is ruggedized in various ways against water, shock, and other elements.

This is the same rating we used to use with the big clunky mobile computers we would use in process plants for collecting data in the field. The ruggedized rating meant these computers could take some pretty rough abuse and keep running, which is obviosuly a necessity in those environments.

Why not use this phone as a replacement for those big clunky computers? The missing element is safety certification. Those old computers were also certified to be safe for use in potentially dangerous environments, which means it shouldnt be able to create an explosion in areas where explosive gases might happen to be leaked.

Most likely this phone is already safe enough to use in those environments, but this does not mean they are certified for such use. The safety certs require the device be put through some pretty harsh testing to make sure that it is not capable of creating sparks etc. Once the certification organization has proven this, it receives the certification for the level of dangerous use it has been tested for. This process is not inexpensive, and since it is only useful for a relatively small sub-market of mobile computing, not very many devices get this process done.

In addition, just because these new phones are way smaller and lighter than their predecessor, this doesn’t mean they would be a good fit for service in industrial environments. Imagine wearing gloves to try to activate a touchscreen – this is why industrial mobile computers still tend to use big keyboards. Also, battery life is already a problem on most modern smartphones, so imagine needing to use them in the field for hours on end- unless a much larger battery can be fitted, it just isn’t going to happen.

These devices might find a fit in some semi-industrial uses though. A worker or foreman who spends shorter periods of time in the field, but still needs a device that can handle the environment, could be a good fit for this new phone.

It will be interesting to see any third party companies try to adapt this commoditized technology in a way it can be further utilized in hazardous industrial environments.

A timeout was reached (30000 milliseconds) while waiting for the….

A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect.

 

My new and really fast laptop has been occasionally freezing all input for a long period.. maybe a minute, maybe more.. and then suddenly unfreezes and catches up. I can still move the mouse around, but no clicks and no keyboard input is accepted.

 

What the heck?

 

The error above is what I found in the event viewer after it just happened today.

 

Any solutions out there?

 

Running Windows 8 64, Dell XPS 15.

 

A big ol SSD too. Hope that’s not going out…

 

 

Update: I’ve noticed this error shows up in searches for a lot of similar errors, such as:

a timeout was reached (30000 milliseconds) while waiting for the windows error reporting service service to connect

a timeout was reached (30000 milliseconds) while waiting for the print spooler service to connect

a timeout was reached (30000 milliseconds) while waiting for the file replication service to connect

a timeout was reached (30000 milliseconds) vmtools

 

and also while waiting:

for a  transaction response from the VMTools service

for the Symantec Endpoint Protection service to connect

for the SQL Server Reporting Services service to connect

a transaction response from the AudioEndpointBuilder service

a transaction response from the ShellHWDetection service

 

Ok so the list is too long…