natevw proudly presents:

a glob of nerd­ish­ness

powered by work over time.

Metakaolin Mobile v1.0

It took more time away from client work than I had planned, but it did "ship" in time to enter Mozilla's Dev Derby.

Picture of an exhibition

Try the demo entry

Still waiting to see how the judges liked it and nervous that its unique editing interface was a big strike against it as a casual demo. Still needs some visual and touch size improvements to the vector editing. No feature sketch mode. Needs a better solution for caching the map tile set(s) separate from the app. Doesn't yet show your current location. CouchDB sync code commented out. Etc. Etc.

However, a number of features that weren't in the original early editing platform are now there: you can name each shape (or actually enter custom JSON), pick colors, choose from a handful of basemap options, delete unwanted documents, etc. And of course, the first pass at an offline mobile-friendlier interface.

comments

Numbers.app spreadsheet template for 2012 IRS Form 1040

This year I'm trying to get a head start on taxes, so I've already updated my traditional Numbers template. This is an unofficial, potentially incorrect, use-at-your-own-risk spreadsheet for unofficial, potentially incorrect etc. tax preparation number crunching. I use it so that I can gradually prepare my return as I collect all the correct numbers, as well as to get some quick estimates to answer questions as I prepare (e.g. is this deduction form worth the time it will take to fill out?).

Title/header of first spreadsheet page

This spreadsheet is only optimized for basic personal/sole proprietor/small business taxes, but within the basic 1040 form it's rigged up to automate just about as much as I could. It was fun many years ago to turn the form's IRS instruction tables/logic into its raw algorithmic form, and now it's fun to not need to sign up for some spammy scammy "file your taxes online for free(asterisk asterisk asterisk)" e-File thing. When I've got everything figured out in the spreadsheet, I then copy it to a the IRS's PDF forms and print on a stack of good old paper for mailing.

You can try it out by downloading my f1040-2012 Numbers template file — it should open as an "Untitled" doc you can save to a new spreadsheet. Would love to hear if you find it useful!

Update: posted a revision which adds a small Schedule A table, half of self-employment tax deduction, and slight update to the mileage rate.

comments

Sketches of a mobile-friendlier Metakaolin

Sketched out some interface ideas for making a better overall experience for Metakaolin on mobile, right on my tablet instead of my usual pen and paper. Even harder to read my writing (I used my Cosmonaut, but without being able to rest one's palm a stylus isn't much help) but on the other hand it's a bit easier to share the ideas online. Still working out which bits to implement for the first "offline" iteration, but here's a handful of ideas I'm excited to implement at some point:

Editor overview

The first idea comes inspired by a great patch by Brian Mount. I'd like to add a "+" button that simply adds a single point in the center of the map when tapped, but when held lets you just sketch out shapes with your finger! This is a refinement from Brian's demo, since it retains the original editor's modelessness, which is its most important property. The interaction on desktop will likely need a modifier key to retain the intended quasimodal design.

The next thing I'm excited about is showing the current location for reference. The idea being that if you're out on site and want to adjust shapes relative to your device's built-in GPS reading it will be displayed live on the map underneath your vectors.

The rest is pretty basic adjustments to the layout and touch target size fixes. I'm not quite sure how well this design will scale up, off of mobile onto a large desktop screen, but I may take some ideas from the recent Android Action Bar interface element and unoverflow items out of the menu into the bar when there's more real estate. A few other items (i.e. the zoom control) would ideally only show up if/when needed (i.e. single touch device).

One key touch target adjustment is the editing interface itself. Currently the perceived affordances that would lend intuitiveness to the simple but relatively powerful interface are weak on desktop, and almost completely missing on direct touch devices where there is no hover feedback. I think by enlarging the width of connections in a bit of a creative way, I'll be able to tackle two problems simultaneously: making the lines easier to grab and refine, and making that interaction easier to discover in the first place.

Detailed look at vector affordances

The trick here will be drawing those "bumps" programmatically, but I think it will be worth the extra coding effort. The node side of things gets a little TLC too, better showing the temporarily sticky add vs. normal move state. After practicing with the large grab handles to sketch more real shapes on the map (instead of cartoon ships and trucks!) it's also clear they should be made as small as still practical and perhaps a bit less opaque so they don't cover the basemap as much. While I'm implementing a less "lines and circles" barebones display it'll be a good idea to add a soft contrasting halo around the shapes as well. This would serve both to increase the touch hit area and to make sure the drawing stands out above any basemap terrain/background color.

I'm not terribly happy with the native-app-mimicky appearance that some elements of the overall design seem to imply, as I believe the web is (or at least should be) its own platform. Even as it goes mobile and offline, I don't want Metakaolin to become a cross-platform app — it should be a web app. What that looks like and what that means, especially considering that this is manipulation software for which no browser provides any standard/native controls, is another topic that I still don't claim to be halfway qualified to write about yet. I hope, though, that the fruits of this concern can remain apparent as Metakaolin — and Shutterstem and others — continue to develop.

comments

MapBox Satellite

I started building Argyle Tiles to provide a beautiful and global satellite/aerial imagery dataset, with as few license restrictions as possible, because in a world where generating a custom street map has become almost trivial, I felt this complimentary service was still lacking. Seemed like it was high time someone did it, and tried to do it well.

Last week, MapBox released a gorgeously processed imagery layer as the newest part of their service offerings — they've gathered up all the great public domain data that was on my list and delivered it already. And they're not stopping there. I've long been a fan of their work (the open source tools MapBox has shared are a big reason OpenStreetMap data is now so easy to display), and I'm confident they will be able to deliver on their announced plans for MapBox Satellite.

In light of this, I'm scaling back plans for Argyle Tiles as a business.

Argyle Tiles deemed unnecessary

I had already been struggling with how to deal with the encouragement I'd received: everyone was eager to see the product done. As in, "Let us know when it's done!" At the rate I was able to personally invest in the project, it would have been many more months before just a handful of major US cities were deployed, and the estimated cost per interested customer would still have been discouragingly high. Then how far out dreams of going beyond the available public domain data would still be! I decided to press on, though admittedly not in a particularly diligent or focused way; now I'm glad the burden is no longer on me. Between MapBox Satellite (beautiful and affordably priced) and MapQuest Open Aerial tiles (still available without charge), I no longer see much of a need for my independent offering.

I don't intend to shut down the existing URLs anytime soon, and may continue to dabble with the many interesting challenges of hosting terabytes of images and/or building a sustainable business. Most likely, I'll move the data out of expensive cloud storage to somewhere I can more cheaply (albeit less reliably) play with a much larger set. I'd also like to contribute the bits of tiling code and some of the (still-in-progress) parallel processing infrastructure to OpenAerialMap, which IMO has languished far too long and might benefit from a bit more of a "product"-like vision. I seem to remain all too adept at non-profit products, so perhaps pure open source projects are a better fit for my ideas anyway.

(Always happy for more consulting and freelance development leads, by the way. I love tackling hard problems, like designing custom maps or architecting CouchDB apps, working for honest people — like the continuing set of new clients I was blessed with this past year!)

comments

Printing my first part

Since putting my Printrbot to work in September, I've printed many things:

All of these were from files others had made and posted online. Transmitting just the bits to wherever the atoms are needed is incredibly nifty, and it's neat to even see hardware companies get involved with its potential.

But it was really rewarding to finally sit down last week, and work at some 3D modeling software long enough, to print my own design! I used SketchUp to draw out a simple but effective version of a microwave turntable coupler that was missing from Room to Think's microwave:

SketchUp screenshot First iteration on printer New part in microwave

It took a bit of iteration, especially with my calipers left at home. Since I couldn't figure out how to adjust things like a circle radius that won't just push/pull I actually started from scratch each time, but it was good practice and it's reasonably fast to draw out new parts.

(It certainly must be rapid prototyping when it is easier to just try a couple prints than get decent measurements!)

This type of thing might be a better fit with OpenSCAD for easier adjustment, but the SketchUp files and an STL export are shared on Thingiverse in case anyone else ever needs one close to this size/shape — it's a lot cheaper to print a second copy, once the unpaid CAD work is done!

comments


All posts

Subscribe