Red Sweater on iPhone
-
[9:05 AM]
Red Sweater Blog: "Since Apple opened the floodgates to the AppStore for iPhone and iPod touch, the amount of anticipatory feedback I am getting from customers has exploded. Not a day goes by without messages from hopeful customers asking if and when my applications will be available for the iPhone. In particular, Black Ink and MarsEdit." - I'm a big fan of Red Sweater Software, I'm using MarsEdit to publish this welbog. iPhone and iTouch apps are a natural for the two applications he's decided to offer. I think Black Ink in particular could be big for Red Sweater. It would seem games are a big win in general for mobile devices.
Labels: Applications, iPhone
comment
Missing the point
-
[9:02 AM]
Free Software Foundation: "Unfortunately, we are not. The extreme here is represented by Jobs and Apple. The iPhone is an attack on very old and fundamental values -- the value of people having control over their stuff rather than their stuff having control over them, the right to freely communicate and share with others, and the importance of privacy." - Wow. The first item in their five reasons to avoid iPhone 3G says "iPhone completely blocks free software. Developers must pay a tax to Apple, who becomes the sole authority over what can and can't be on everyone's phones." Tax? It's strange someone at the FSF would speak of taxes, the GPL is a tax. Sure, I can get my free software and compile it on my box, but where's the integration? My Mac in combination with my iPod is a complete, beautifully integrated, solution. It's the same with the iPhone. It works with desktops and laptops and Apple TV. I can create free applications and Apple will handle the distribution for me. Hey, that's kinda nice. Open source has its place and if you want it to become the dominant force in the software world here's a tip, write better software. Write it for folks like my grandmother, not for me. That means paying attention to all the little things, just like Apple does. Remember guys, the user interface IS the application to the end user, they could care less about the cool algorithm you implemented under the hood. Seriously.
Labels: Apple, iPhone
comment
iPhone 2.0 is a monster
-
[8:49 PM]
Gizmodo: "It looks like not everyone in AT&T land loves the iPhone. When reader Dennis' mom went to the AT&T stand in the Moorestown Mall in New Jersey to ask about iPhone insurance, they laughed in her face. They then handed her a bunch of articles written arguing for the BlackBerry over the iPhone, printed from places like Crackberry.com and Pocket PC Magazine. At the end, there was the name and number of an AT&T regional manager." - My brother tells a similar story. He called AT&T and the customer service lady was frustrated with answering iPhone questions. He said she sighed when he said he wanted to talk about iPhone pricing and plans. I guess it's succeeding, everybody hates 'em.
Labels: Apple, iPhone
comment
Job of the week
-
[9:34 PM]
jobs.joelonsoftware.com: "How would you like to work from home, writing code for the hottest new mobile platform, the iPhone OS?" - How's that for an opening sentence?
Labels: iPhone, Life
comment
Twenty iPhone applications
-
[9:06 PM]
Macworld: "With Apple’s iPhone App Store now online, we decided to take a look at some of the more interesting third-party programs, applications and Web sites that have been developed to help make your iPhone an integral tool for both work and fun."
Labels: Apple, iPhone
comment
New iPhone apps
-
[9:08 AM]
Apple Gazette: "After spending the last hour or so rummaging through the iPhone App Store in iTunes there are several applications that I just can’t wait to get my hands on." - One of the five applications has a horrible UI, TripLog/1040, very much not what you'd expect to see on an iPhone.
Labels: Apple, iPhone
comment
LG Dare, dead on the vine
-
[9:07 AM]
Apple Gazette: "The phone will retail for $250. You then get a $50 mail-in-rebate…which will bring the cost down to $200 when you eventually get your rebate check in the mail." - The only chance this phone has to compete against the iPhone, it's one and only chance, is it's offered by Verizon. If you don't want to switch networks you have a phone that is a distant second to the iPhone's design. We're going to see tons of clones now, but that's what happens when you're the best of breed.
Good luck with that LG.
Labels: iPhone, Technology
comment
Brent Simmons, mad man!
-
[4:40 PM]
Brent Simmons via Twitter: "Finally put NetNewsWire for iPhone in svn. Was relying on Time Machine and scripted backups." - Wow, that's something I'd have done straight away, but I'm paranoid like that.
I think the bigger thing to take from this post is we're getting NetNewsWire for the iPhone. I look forward to using it.
Labels: Applications, iPhone
comment
I'm not fussed about it
-
[8:10 PM]
Daring Fireball: "Talking about technical progress only serves to focus attention on the fact that it is Apple’s decision, and by all appearances, Apple does not want Flash on the iPhone. Even if Adobe eventually gets Flash running well — by any standard for “running well” — on actual iPhone hardware, rather than just in the iPhone simulator, they can’t ship it without Apple’s explicit permission." - I really don't think the iPhone needs to have Flash support. Apple has gone to great lengths to make sure the experience is what you'd expect from an Apple product. Like the decision not to allow background tasks, I'm OK with that as well. Why? Allowing applications to run in the background comes with its own price. I don't own one, yet, but that will be remedied July 11. I may not have one, but my wife will, and that's essentially like having one myself.
Labels: Adobe, Apple, iPhone
comment
More on iPhone 2.0
-
[8:32 PM]
Popular Mechanics: "The first would be the addition of a GPS antenna. I recently sat down with the president of a GPS navigation system manufacturer to ask him how he felt about the prospect of a GPS-enabled iPhone. "Scared [expletive]-less," he said. Hardly a rarity in the handset world, GPS functionality is already used by many carriers to sell location-based services and for Emergency 911 (or E911). And the iPhone already does rough location positioning by cross-referencing tower triangulation with a database of known Wi-Fi hot spots." - Yes, I want one.
Labels: Apple, iPhone
comment
iPhone 2.0 Shipments?
-
[8:51 AM]
Fortune: "Searching for shipments to Apple, Inc. (AAPL), employees at the Scottsdale, Ariz., company reported on Friday that they’ve spotted a 'major spike' since mid March in ocean containers marked with a mysterious new label: 'electric computers'" - Hey, even if it's not true, it's fascinating to watch the frenzy developing around iPhone 2.0. If I said I didn't want one, I'd be a big fat liar.
Labels: Apple, iPhone
comment
iPhone experimentation continues
-
[9:12 AM]
I've been exploring the iPhone SDK lately, it's been fun. I've finally figured some stuff out so it's really starting to get exciting. My "big" hurdle had been understanding how to take advantage of Interface Builder. I finally figured out how to hookup events now that seems pretty obvious, I knew that would happen, light bulb on, bing!
Here's a question for any Mac developers. Do people actually use the Interface Builder to design visually and hookup events, or do they draw the interface and hookup events in code, or do they build the UI all in code? I know, it's a strange question, and I'm sure I'll get a strange mix of answers, if any at all, but I had to ask. I'd love for Daniel Jalkut, or Brent Simmons to chime in.
Doing Windows C/C++ stuff for years had led to a certain expectation with Mac tools. In Windows I only used the graphical tools to create dialogs (at Visio we didn't even do that), then I'd go hook up event handlers in code. It was very straight forward and after using Interface Builder once I can see how easy it would be to hookup events in code instead of letting Interface Builder generate code for me.
I was very happy to discover a hunk of old C++ code compiled and worked like a charm when mixed with Objective-C. It was a pharmacokinetics library my brother and I created a long time back, and it just built and worked. That is a HUGE leg up for me. I can use my bad habit of writing C++ and slowly move into Objective-C. Very nice.
Next hurdle, gaining a better understanding of Objective-C.
It sure would be nice to build a Cocoa version of the Endura WS5000 software, hint, hint.
Labels: Apple, C++, Cocoa, Development, iPhone, Mac, Objective-C
comment
Refurb iPhones?
-
[4:36 PM]
The Unofficial Apple Weblog: "I bought one of these up last time round. This time, you can pick up a 16 GB iPhone for just $349 or an 8GB for only $249. Free shipping and a full one year warranty" - This is a nice way to get a phone, not only for personal use, but for development purposes! Don't want to brick your main phone, do you?
Labels: Apple, Development, iPhone
comment
I really, really, want to go to this
-
[9:48 AM]
Apple.com: "The groundbreaking innovations of Mac OS X Leopard and iPhone OS offer two revolutionary development platforms for developers and IT professionals. The Apple Worldwide Developers Conference (WWDC) is the only place you can receive technical information on these sophisticated platforms from the engineers who created them. Bring your code to the labs and work one-to-one with Apple engineers, applying development methods and best-practices you gain from sessions to enhance your application."
Labels: Apple, Cocoa, Development, iPhone, Mac, Objective-C
comment
