3 ms·
. . . but then you aren't really developing on an iphone, in any meaningful sense anyway - all the "iphoneness" has been replaced, so it's effectively no differ
by klochner 15y ago
. . . but then you aren't really developing on an iphone, in any meaningful sense anyway - all the "iphoneness" has been replaced, so it's effectively no different than any apple device with a cpu - ipad, mac mini, macbook etc.
I think she meant she wanted a touch-screen ui that lets you drag and drop elements into a new app. Doubtful you would get anything complex or terribly unique out of that kind of interface. Certainly no angry birds :)
- dlsspy 15y agoThat's pretty much how all development works in OS X proper. Just today, I needed a simple interactive calculator to think through a problem. It took me about as long to write an app as it would've taken me to make a spreadsheet, but I got to have it be interactive and do what I needed: http://skitch.com/dlsspy/rh8rp/throwaway-app http://skitch.com/dlsspy/rh8rp/throwaway-app
- klochner 15y agocool, is that in cocoa? for some reason I draw a distinction between "development" and writing little utilities for personal use, maybe because my little utilities aren't as pretty.
- dlsspy 15y agoYes. Tiny bit of objective C and enough time in IB to draw my inputs. Much of the mobile development I did was for little things like that. I wrote a utility for palmos to clean up my SMSes in batch because the UI on my phone and the palm both sucked. The most complex I wrote was a call log app that would helped me with a particular problem I was having. Most things were just using it as a fancy calculator or playing around with algorithms or something. I'm not very good at consumer devices, but I think everyone should at least have access to such toys (iLuaBox is a good start).