Tagged with Mobile
If you build PhoneGap apps and test with the browser, moving to phones sometimes causes a boatload of problems. Because there isn't a great debugging story, being able to see the console window would be of great help.
I don't use the Android SDK for development of my PhoneGap apps. I have it installed because I did some early investigation into Android back about two years ago and it was still there. One great thing to say about Eclipse and the Android SDK is that they are simply file-based so when I pave, it still works (still on that drive taking up space). For me this was a lucky break as I needed it to access the console. So how does it work?
After my recent talk on Mobile-First Design, one of the attendees tweeted that he thought it was ironic that my talk was on responsive design but my blog wasn't mobile-friendly. I told him that my company site was…but that was a cop-out. I hadn't had time to get the blog setup with a good template. So voila! I haven't confirmed that everything works the way I want but we should be close!
As some of you might not know, I don't use a blog engine (it's just a custom ASP.NET MVC site). What I love about ASP.NET MVC, is that since the markup so fairly separated from the code (I try and use as little actual Razor markup as possible), skinning it with a new Bootstrap template was pretty simple. It took me about 8 hours to convert it all.
Let me know what you think…
I had a great time at yesterday's online DotNetConf. I think my "Mobile-First Responsive Web Design" talk went pretty well. You can see the talk on YouTube (embedded below). The talk was focused on designing websites to be efficient on mobile platforms by starting with your design on a mobile and scaling up to tablets and desktops.
If you viewed my talk, you might be interested in the slides and source code. You can get them here:
You can view the talk here:
If you're interested in cross-platform mobile apps, I like the solution that PhoneGap has. It uses HTML5/CSS/JS as the UI stack and I find it compelling to build apps for iOS, Android, Kindle, Windows Phone and Windows 8 Store. I've just released a new course on PhoneGap that attempts to fill in some of the holes in building apps. The course includes:
Hope you enjoy the course. You can view it here:
One of the things that I’ve been spending a lot of time working with lately is the ability to be able to build cross-platform apps. While I spend a lot of time in the Microsoft space (especially Windows 8 and Windows Phone 8), I need to be able to create and deploy apps to iOS and Android platforms. I've decided to do a series on building one of these using Single Page Application for the web, then deploying it to devices via PhoneGap:
There are a number of solutions for cross platform apps (e.g. MonoTouch/Droid, et al.) The types of apps I am building are just consuming or displaying information from a standard web back-end (e.g. REST services). Because I typically need to build a responsive website for the solution as well, using a solution that could share some or all of it’s code with the website is a good match.
Using HTML5/JS/CSS to build apps isn’t perfect. Not all apps are a good candidate for this type of cross-device development, but I like to think that for many v1 apps, this is a laudable solution. In many cases, these apps are plenty functional for the life of the app, and in other cases it provides a fast-to-market solution so that a full native experience can be built after the app is initially launched and validates that it fills a market need (classic Minimum Viable Product strategy).
I headed up to the Gwinnett .NET Users Group last night had we talked all about mobile web development using ASP.NET! If you were there, thanks for attending and here are the slides and code as promised!
If you had any questions that you didn’t get to ask at the talk, just comment below.
Just back from the CodeStock 2012 event and I want to thank Michael and everyone involved for a great event. I met a lot of great people and had a great time in Knoxville. Both sessions were well attended. I especially wanted to thank those attendees who attended my 2 1/2 hour marathon session on Modern Web Development (see my blog series on it here).
Unfortunately, my recording software was crashing so the talks didn’t get recorded. For those who saw me speak, here are the slides and demos:
Mobile Web Development
This is the ninth of ten parts of this blog post. The topics will be:
Why do users complicate our lives by trying to view our content on their phone and tablets? It's even an issue for smaller sized desktop screens too. Since this is simply a reality for today's web developer I was glad to see there were real strides in working with mobile.
In general there are three techniques for dealing with mobile device browsers:
In this ninth part of my series on architecting Windows Phone 7 (WP7) applications, i'll discuss threading on the phone. If you've missed the past parts of the series, you you can visit them here:
In the big picture, the applications you build for the Windows Phone 7 needs to super responsive. But the hardware is a phone so you have concrete limitations to what can and should be done on the phone. In the big picture, its usually better to shoot for perceived performance than try to overpower the CPU and GPU. So a judicious use of threading is important.
I am one of the lucky few who received Windows Phone 7 phone this week. For those who will ask, I got a phone because I am writing a book on programming for the Windows Phone 7 (Application Development for the Windows Phone 7 with Silverlight, Addison-Wesley).
My overall first impression is very good. I was able to get e-mail working, XBox Live integration and play with debugging on the phone. This blog entry will exclusively tallk about the phone, not the development experience. I will add new blog entries soon on my experience developing with the phone.
I've been playing around with the new Windows Phone 7 Silverlight development. If you want to start playing with these early CTP bits, you can get them at: