Monday, January 14, 2013

Housewarming

Awww, thank you for the house plant. Though fair warning...I will probably kill it. I have a black thumb.

Welcome to Appartment 325, the new home of Elizabeth Ann West and her journey to become an app developer with 0 programming knowledge. Okay, not EXACTLY zero, I can somewhat understand the overall gist, but I can't read, translate, or write code in any language aside from markup languages like HTML.

When I decided to write a fiction novel, I started a new blog at eawestwriting.blogspot.com. Since this is an entirely new ball of wax, though somewhat related to what I've done before, I figured a new home was a good idea for a few reasons:


  1. I need to chronicle my journey. Back when I was working on Cancelled, some days having my blog to talk about my obstacles and challenges was WHAT kept me going when things got tough. I already expect this journey to be frustrating, it already has been.
  2. By beginning at the start, I make a handy step-by-step guide for people to come after me. Why should computer programmers have all of the fun with mobile apps? Exactly.
  3. I can keep my various business/hobby interests separate and not confuse audiences only interested in one or the other.

So What Are You Planning Now, Elizabeth?

A digital magazine. It has been a dream of mine for over a year now to take what I've learned from writing non-fiction, my ability to lead even the most unwilling, and the appreciative love I have for the graphic arts and marry them into one project. LinQed Magazine. 

In general, when a good idea bugs me this long I'm rather hopeless to give it up. Can I code? No. Have I used Adobe's Creative Suite of products longer than 3 months? No. Is that going to stop me? HELL NO!

I started with the plan to just format the magazine as an ebook. I know how to do that. But the problem is that's like calling a Harley Davidson Powerwheel and Harley Davidson Motorcycle close enough to the same thing. It's not.

Ebook formats can't handle embedded video well. Well, epub can but aside from the Apple iBookStore, epub distributors are mostly a sinking ship still relying on bilge pumps to stay afloat. Eventually, those motors are going to shit to bed. And Amazon's Kindle format can't handle embedded video either, even though the Kindle Fires can. So this means to have a truly interactive magazine, with moving parts and videos etc, I need an app.

Wow. You're brave, are you sure you can do this?

Well to be honest there isn't much out there, yet, about developing Kindle Apps for Dummies (that's me, and I'm proud of it). Because the Fire was so late to join the Android Party, almost all of the guides out there for easy app creation are for Google Play's marketplace, or Apple iOS (which isn't android, but Adobe exports easily to Apple apps).

I am straddling two worlds. I am a member of the geek end user world, but by and large I can't explain very well to other authors what it is I'm excited about at the little step stage. For example, today I managed to export a sample Adobe Flash app in the proper protocols for my First Generation Kindle Fire, sideload it, and install it. All it does is swipe between three panels, but it's a heck of a lot better than my homemade Indesign to Flash attempt that has Tourette's Syndrome by just flashing back and forth between the two spreads. And even that previous sentence, most of my authors friends have no idea what I'm talking about when I say spreads, sideload, and Indesign to Flash. 

The other world I am visiting but NOT a part of is the developer world. I don't speak their language, and I have to be careful on forums and in the public spaces because it's easy for me to ruffle feathers. After all, I'm the equivalent of someone coming into my author forums saying they are going to write a book but asking what is a noun?

Yeah.

Mostly I'm watching tv.adobe.com every chance I get. :)

Plan for Version 1.0

The hardest part of this project is NOT getting so caught up in my perfectionism that my ideal of what's good enough in my head doesn't remotely match up with my burgeoning app developer skills. 

I have identified that there IS a need for clear content for the Gen X/Boomer generation using technology for entertainment, buying digital content, but without a real love for the technical side of things. Everytime they touch their iPad, Kindle Fire, or Android phone, they do so for either work or relaxation. They don't pick it up to have their intelligence insulted or to be reminded at how ignorant they are of what's going on under the hood. 


Nasa. I have to make something with a broader appeal than a Nasa App and a Sun Alert. Seriously.

Now, the paid magazines, the number #1 as I write this is still #755 in the App Store overall. This means that so far, magazines aren't popular enough to overtake the games world. But that's okay, because if there were already a ton of highly ranked magazine apps in the paid store, I'd be screwed. There would be no more room at the table.

But Elizabeth, print magazines already have apps and they're free!

Funny you should mention that. If you read the reviews, most of those users are not happy that the app is free, but THEN you have to pay $1.99 and up per issue, all the way up to almost $7.99! It's not that they don't want to pay for the content, it's that the app doesn't fully replace the print version and in some cases it's more expensive/not included in the price of getting the print subscription. 

Moral of the story? Don't nickel and dime people to death and use false advertising to get them to download a free app with in-app purchasing for anything worth time.

No, Linqed Magazine will be $0.99 an issue. Apps make 70% still on their list prices, and each month will be a unique app unto itself for a number of reasons:

  1. People value what they pay for. As I plan to make the lion's share of revenue to support the magazine from ads inside, I need to make sure my audience is captive enough to interact with the content. If someone pays $0.99, they will at least peruse through the app unlike a freeload spree where Linqed gets forgotten.
  2. This industry is moving TOO FAST as far as capabilities go for me to tie myself down to one app that just does pushes to the "subscribers" devices. First, that will quickly be ignored. Second, I need flexibility to stay current with the latest capabilities of devices and most importantly, what readers WANT.
  3. There's no money in a subscription model for CONSUMERS. First, a magazine doesn't necessarily need previous issues to make sense. No, an issue should be a self-contained product, much like a novel is, even in a series. Now, let's say I have an author who wants to serialize a short form novel across four months. We can do a quick summary "Alex is staring down her fiancee after just learning he is having a baby with another woman...." and state that the earlier installments of the story are in Issue X, Y, Z with links for the customer to go get them IF this part of the magazine is what interests them.... Most app customers want to use an app and then move on. It's more like an ebook in terms of consumption than many think. Even games, there's a reason there are like 20 versions of Angry Birds.
  4. More apps builds my developer name more and more making visibility higher. There's a difference between a one off app and an app developer who has 20 apps out on the marketplace.....
  5. I can always make back issues FREE. Apps still enjoy the ability to just price the app for free.


I am at a fork in the path right now. Originally I was going to try to use a nifty "Make my Indesign file an app" service. 
  • Services like Adobe DPS (which requires a Mac first and foremost) or 3rd party services are $1,000 or more PER ISSUE and per platform. That methodology lost out pretty early.
  • Next, I decided I would just learn Java. It can't be that hard, right? Once I started doing that (I made it to Chapter 4 of an intro to Java programming book) I realized that method would completely kill my joy in this project. Severely. I don't want to ruin the artistic side of the project by interacting with down at the file call out in the proper syntax. Blech.
  • Finally, I've realized a number of the tools I already pay for with my Adobe Creative Suite membership will make Android and iOS apps. It's just not quite click. done. So this is where I am right now.
But, do I try to figure out how to make Indesign to Flash, or just Flash from the get go? The only hesitation I have is that by designing in Indesign first, I have more power to export to PDF, epub, and even Kindle formats with just a few modifications, and it will support the multiple layouts and liquid layout designs (fancy speak for making the magazine adapt to the screen size it's viewed on and the orientation it's being held in. Yes, super cool.)

I need to find out if Flash export to InDesign. I don't think so. 

I also need to learn if the bug I experienced today is a common thing. Is it too much of a bastardization of the developer process to get used to going InDesign --> Flash Pro? In other words, am I making a bad habit by not learning Flash Pro more first?

So tomorrow is a new day to do more research and play around. Again, welcome to Appartment 325, home of one wacky author who woke up one day and realized she needed to become an app developer.





No comments:

Post a Comment

Post a Comment