6 ms·
That's a strange statement. It's a very simple app, which specific guidelines do you think should have taken significant time for him to write code that complie
by _-___________-_ 7y ago
That's a strange statement. It's a very simple app, which specific guidelines do you think should have taken significant time for him to write code that complies to?
In my experience the guidelines are mostly common sense once you get used to the "Apple way", and are straightforward to comply with, especially if you're already familiar with them (OP had submitted several apps before).
- mister_hn 7y agostill, claiming to hacking a mobile app together in one hour is something strange as well. Does the "hour of code" includes setting up project in the IDE, setting a repo, testing it, making it AppStore-ready? Options are: a. you have already the code somewhere (own sources, StackOverflow, GitHub, etc.) b. you are bluffing
- trevyn 7y agoMy first app store submission was a challenge to go from idea to submitted app on one laptop battery charge (2-3 hours?) and was approved on the first try, so it’s definitely possible.
- samwhiteUK 7y agoSounds like you need a new laptop
- rumanator 7y agoI have no experience with iOS development but I do have in Android, and in Android it is quite possible and even uneventful to put together an application that allows users to navigate through half a dozen activities and fragments in about an hour of work.
- RugnirViking 7y agoSetting up a project in the IDE takes maybe a couple minuites at worst. you wouldn't bother making a repo for something like this. Testing is done while programming, and the process of putting it on the app store presumably wasn't counted as 'programming'
- maccard 7y agoDoes it even? Last time I checked, it took <1 minute to launch xcode, use a template and deploy it to a device (assuming you're set up to develop already). Every IDE I've used in the last decade will detect "hey, you're starting a new project, would you like a git repo?"
- TheSpiceIsLife 7y agoWhere do you draw the line? Does the 1hr include the hour you spent driving to the shop and back for a loaf of bread and a bottle of milk?
- bengale 7y ago> setting a repo `git init`? Clicking create repo in GitHub? > setting up project in the IDE are you doing this stuff blindfolded or something?
- mister_hn 7y agoyou forgot the "git remote add" part. That takes a couple of minutes
- codesternews 7y agoThere are many open source project which have drag and drop gesture and all the needed feature. He just might have to combine two projects and some programming and replacement of icons.
- fingerlocks 7y agoI could believe it if you counted only the time taken to type just literal code. Probably discounted the time it would take to build the UI .xib, wire up all the event-handler delegates, and set all your layout constraints for the various screen sizes. And doesn't this use the camera and/or photos API? Not hard, but somewhat time consuming to set up your boilerplate for these. Also handling permissions request, response, & error handling. Probably copy/pasted from another project so it wouldn't count? Yeah I'm skeptical, but also sounds like a fun challenge.
- deleted 7y ago[deleted]
- megablast 7y agoLoad xcode, create a project, setup a repo can take 10 seconds. I just did it. Testing it takes longer. You can create a blank app and install it on a phone in 30 seconds. It really is that quick. Of course, writing it in 1 hour is a bit ridiculous. Did he have the icon images ready?
- gmueckl 7y agoThe article states that icons and other polish is excluded from that time and were done later.
- bryanrasmussen 7y agoI'm supposing that he naturally made the project appstore ready because he knew what the requirements for that were, as in he did not write what he needed and then fixed it, he instead did not write anything that went out of guidelines. As far as the other stuff, this reminds me of recruiters who send you a coding project that they say will take 2-3 hours that generally takes 4-6 if there isn't some major problem. The extra time is of course setting everything up choosing what dependencies you need etc, because every project is slightly different and you are unlikely to have everything that is needed for that one project. The actual coding is probably 2-3 hours. So perhaps he already had everything his system needed, if so I expect it might have taken 1 hour to code (because he was very comfortable and knew exactly what he would need to do) and some minutes to make git repo, push code. Then add another hour to time compiling and submitting to app store. If he knew what he needed to do in the code of course that was probably from thinking about it for weeks beforehand.
- tannerc 7y agoThis is accurate. I should have possibly mentioned in more detail that at the time I had a lot of experience with prior apps, so whipping another one together—particularly for such a simple concept—is trivial. I’m surprised anyone here thinks something like Snaplight would take more than an hour to build (no repos, testing on device but otherwise no tests, simple permissions, uncomplicated UI that only improved post-launch, etc.).
- Liquid_Fire 7y ago> I’m surprised anyone here thinks something like Snaplight would take more than an hour to build I think it would take me longer just to make the icon, having never done anything like that before. Think about all the skills you had previously built up that allowed you to make it in an hour. If someone lacks even one of them, they would never be able to do it so quickly.
- giarc 7y agoLikely just used some stock icons or had previously designed them for another project and never used them.
- tannerc 7y agoI’m a full-time designer and designed everything in the app from scratch.
- sizzle 7y agoHi Tanner, big fan of your design portfolio. As a fellow designer, what inspired/motivated you to make the jump into learning how to code? Was it simply scratching the itch to make higher fidelity prototypes? PS- should designers code? ;)
- tannerc 7y agoThank you for the kind words! I started coding long, long ago in order to build my web portfolio (back before site builders were a thing). As a result I saw how empowering coding can be. I've always felt being able to code software gives you an ability to solve a lot of your own problems with technology. e.g. I have a lot of private tools I've designed and coded to help me in my day job (such as this simple one I recently open sourced: https://tannerchristensen.com/spf https://tannerchristensen.com/spf). If you're a designer who works on digital products, I think it's only advantageous to know some programming. It gives you empathy for your engineering peers, gives you more insight into how what you design will actually get built (and the constraints/advantages of the technology), and helps you see problems in different—often more linear and logical—ways. Learning to code is not for everyone, but learning a little can go a long way. At least learning the basics of code structure, loops, memory allocation and management, etc. would be my suggestion.