My Process for Creating APIs
My Process for Creating APIs
Join the DZone community and get the full member experience.Join For Free
@fogus asked an interesting question this morning:
How do lang/lib creators know what's best for the average programmer when what they try to solve is nebulous or underspecified?— fogus (@fogus) September 8, 2013
@fogus I throw stuff up against the wall and promote what sticks. There’s plenty of fail experiments I’m Lift.— David Pollak (@dpp) September 8, 2013
But that's not the whole story... so, I'll outline some of the processes that I use to create APIs and code.
I'm My Own User
I brought Buy a Feature to life and along with it, brought Lift to life. Buy a Feature is a multi-user online game and it's entirely HTML browser based and had to work with IE6.
Most of Lift's Comet features are there to support real-time pushing of data between game players... in IE6.
So, many of Lift's early features came from doing Buy a Feature.
I Love Going Against the Grain
I'm a trouble-maker. I like going against the grain. So, when the whole world is MVC, I look for something different. Specifically, I look for ways to make the APIs reflect the way developers work. Thus, Lift is "view first" because developers do mock-ups first and fill in the functionality. Rarely have I seen a developer "write a controller on a white board." Nope, they lay out the screen on a whiteboard and go backwards from there. Why not have code the reflects that.
Stealing and Improving
I love stealing other peoples' excellent ideas... especially when those ideas are outside the realm I'm working in.
So, Lift's GUID associated with server-side functions is just a web representation of references. Why carry state around in the web page, when it can be carried as a reference to a function that closes over the state server-side. It's just a way to treat Scala functions the same way across address spaces. It's also a Scala/Lift rip-off of Seaside's Continuations.
I am a security nut. Part of what drives my API designs is ways to make it easier for the developer to write secure apps by default. So, when I'm writing APIs, I try to figure ways to keep data reified until the last possible moment rather than converting things to strings or other un-typed data early. But this has to be natural for the developer.
Trying Stuff Out
Watching the Mailing List
I also watch the Lift mailing list and see what kinds of things people are trying to do and then write APIs for common threads of what other folks try to do.
I wrote Lift's RestHelp by writing the API, documenting it, seeing where the documentation looked ugly, and revising the API to make the documentation cleaner. It was an interesting 3 days of solid "how can I make this cleaner and easier to understand?"
I think this is the most virtuous way to write APIs and I hope to do more of it in the future.
Published at DZone with permission of David Pollak . See the original article here.
Opinions expressed by DZone contributors are their own.