A Slice of App Pie

A Slice of App Pie

The Newsletter for Creative Indies

Episodes

  1. 10/10/2017

    "Am I a Fraud?" The Plague of Impostor Syndrome, and What to Do About It

    In the middle of trying to get five projects done, I’ve been hearing a lot about Imposter Syndrome. A week or two ago came an article on LinkedIn about Impostor Syndrome in programming. Ever since I’ve seen an article pop up here or there. I've known this all too well for so much of my life it resonated with me. For those who want the shortest version of a definition, I defer to Musician Amanda Palmer. When I read her book The Art of Asking, I found wasn't alone in this anxiety, though she called it the Fraud Police: The Fraud Police are the imaginary, terrifying force of “real” grown-ups who you believe—at some subconscious level—are going to come knocking on your door in the middle of the night, saying: We’ve been watching you, and we have evidence that you have NO IDEA WHAT YOU’RE DOING. You stand accused of the crime of completely winging it, you are guilty of making shit up as you go along, you do not actually deserve your job, we are taking everything away and we are TELLING EVERYBODY.(1) If you’ve ever been successful at something and then look around you and think that your coworkers are so much smarter and better than you and you don't deserve your success, you’ve been hit with Impostor Syndrome. When you get into a panic when you are afraid someone will find out you don't know everything about your topic, you’ve been hit with impostor syndrome. I think, on an everyday basis, I do feel like every one of those in some way or another. I've felt that way for much of my life. But somehow I got control over it. I'd like to explore what I do and think. Before I do, I want to point out a few things. The most critical is you can’t know everything. In any discipline, there always more to know that is knowable. What compounds our ignorance is what I’ve called the Red Queen Dilemma, referring to Lewis Carrol’s Character in Through the Looking Glass. "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" Technology does this to all of us. Standing still is falling behind. Moore’s law makes it impossible to learn enough. By the time you learn one thing, the world changes on you. A year ago, my Book Practical Autolayout for Xcode 8 went obsolete three days after publication. One critical menu selection, the resolver, moved to a toolbar button, making the entire book’s tutorial obsolete and indeed confusing to use. Secondly, there is a paradox of huge social pressure to appear super competent and successful. When your colleagues and friends post only their successes online, it becomes too easy to measure yourself only by their successes. In those you aspire to be, you don't see all the pain and failure in getting where they are. All evidence is to the instant success, and everyone posts success when you are feeling the failure and pain of working towards success. Thirdly, imposter syndrome is a pandemic among successful people. If you have great or small success, you’re probably going to feel at least one you didn't deserve it, because you don’t know what you are doing. While Amanda Palmer might be famous in the world of music, her Husband, fantasy author Neil Gaiman is arguably a Literary rock star. Yet he tells a story about one time he really felt Impostor syndrome: Some years ago, I was lucky enough invited to a gathering of great and good people: artists and scientists, writers and discoverers of things. And I felt that at any moment they would realize that I didn’t qualify to be there, among these people who had really done things. On my second or third night there, I was standing at the back of the hall, while a musical entertainment happened, and I started talking to a very nice, polite, elderly gentleman about several things, including our shared first name. And then he pointed to the hall of people, and said words to the effect of, “I just look at all these people, and I think, what the heck am I doing here? They’ve made amazing things. I just went where I was sent.” And I said, “Yes. But you were the first man on the moon. I think that counts for something.” And I felt a bit better. Because if Neil Armstrong felt like an imposter, maybe everyone did.(3) There is one thing that clears our Impostor Syndrome like sunlight through fog. I do something simple but not very easy: I admit my ignorance. THat’s simple enough but all those pressures I just discussed do not make it easy. Yet that's only half the solution. The full solution is “Yeas I don’t know it now, I’m learning it” I can learn more. I can do the research. I can use the knowledge I have to wing it. Ignorance about any one thing is temporary. You can learn and discover more, and with what you have improvise. One must always be learning. I have found that the best way to learn is not just to admit I don't know but run to find what I don't. For years on MakeAppPie.com I picked one iOS development based on stuff I don't know, research the living daylights out of it, write and post an article. Let me give a very personal example. I’m familiar with what we all fear in Imposter syndrome since that fear became a real-life nightmare for me when I was in second grade. I’m color blind, but I tried my best back then to not do anything different than anyone else. The February of second grade, my class was coloring images of Abraham Lincoln’s face. I picked up the sea green crayon instead of the flesh(now peach) crayon. So Abraham Lincoln's face was sea green. The teacher, Mrs. Sweet, decided that I was to be punished for this by standing me in front of the class with my seasick Abraham Lincoln. She ridiculed and yelled at me, with all the students laughing at me seated around me in that u-shped desk arrangement. I was devastated, and as much as the teacher eventually got reprimanded by the principal after an irate call from my mom, I’ve never forgotten that — it’s a fear it will happen again that fuels my Impostor syndrome. But head forward in time to grad school. I was taking Educational Psychology for my Master's Degree In Education. Of all the topics to pick for my final term paper, I picked the psychology of color in education. I read everything about color, starting with Goethe and Chevreul, Johannes Itten, Josef Albers, and through the use and the use of the then relatively new RGB hexadecimal codes on the web and HSB sliders in Photoshop. I learned about the color wheel, read research about psychological effects of Color and read successful and failed research on color in the workplace. I learned how difficult it is to measure the effects. I had my first of many times reading about Hawthorne Electric and the Hawthorne effect. Along the way, not only did I get an A on the paper and in-class presentation, I also learned to paint (though I avoid green paint - I mix my own) In all these stories I want you to notice something. Everyone fears their colleagues will expose them, all the while their colleagues are afraid of the same. Meanwhile, those with no knowledge think the whole crowd is geniuses, not frauds. The only exception is a few trolls who get off knocking down anyone, to increase their status by lowering and hurting others. In retrospect, that 2nd grade teacher was a troll forcing discipline on her students. The troll really is the only fraud here. Everybody else is genuine. You have little to fear. Let's stop thinking about being an impostor and change the focus on what makes us professionals, because that’s the overarching cure for Impostor Syndrome. Not the definition of professionals such as doctor or lawyer, a more ideal yet pragmatic one that fits in the arts, sciences, business, and sports.  There are two quotes I like about being a pro. One is Stephen Pressfield’s : The amateur plays for fun. The professional plays for keeps. To the amateur, the game is his avocation. To the pro, it's his vocation. The amateur plays part-time, the professional full-time. The amateur is a weekend warrior. The professional is there seven days a week.(3) Amanda Palmer’s definition of a pro is this. In both the art and the business worlds, the difference between the amateurs and the professionals is simple: The professionals know they’re winging it. The amateurs pretend they’re not.(1) Distilling both of those definitions come to this: A pro shows up every day and does the work. Nothing stops the pro, especially his or her own inner resistance, that which tries to prevent you from doing the work and succeeding. Resistance is always there to attack, often with the impostor syndrome's “you don’t know enough, you are not qualified.” The pro knows enough that they can improvise, research and learn, thus always moving forward, no matter what. Palmer and Pressfield both point to think less about being afraid of our inferiority and more about being a pro. Showing up every day, do the work, and winging when we don't know, then admit to ourselves and even others that’s exactly what we do. Though I don’t remember him writing directly about impostor syndrome, I suspect from my reading of his book The War of Art Pressfield would consider Impostor syndrome just another manifestation of resistance. If that is true, then it would also be true that turning pro, keeping the discipline of doing the work, combats resistance and the impostor syndrome. The way our world is structured you’ll feel at times like you you are a fraud, and impostor in what you do. For some, they shake it off. For others, it can become resistance to thier goals. For others, a debilitating fear of sucess. Writing this, I had a few bouts of “who am I to write about this, when I don't have a degree and fifty years of experience in Psychotherapy?” The answer is that I face this demon every day, and I’m a good observer, a good reader, and I’m improving as

    11 min
  2. 12/19/2016

    Happy holidays, Parse a String to a Double.

    Hello all. This week, I’m writing on the website about converting strings into doubles. For some cases this is easy, but if the string is a time or a fraction, it’s not so simple. We’ll look at how to parse these strings into Doubles.  You'll find a Swift Playground file there to experiment or use the functions I came up with to convert strings. It’s the time of year for the holidays. Apple closes down just about anything a developer or author wants. I for one missed my deadline for updating books. All the updates will happen in January 2017. I’m scheduled for early January 2017 to record the next courses for Lynda.com, after I’m done there, it will be book concentration time. Most people tend to go for a holiday special or do reruns over the holidays. I’ve never done a holiday special before, but I’d like to do one today. I’ve been doing a lot of thinking, some of it works here, some does not. Sitting in Starbuck’s with the Christmas music blasting too loud has me thinking about the season There’s one story that’s ancient. It was compiled into a biblical commentary called Avodah Zarah, a name that sort of translates into “dealing with idolators.”  It was compiled 1800 years ago, but I would venture to guess it is far older than that. The story I’m thinking of concerns Adam and Eve, just after their expulsion from the Garden of Eden. The days begin to get shorter, the nights longer. Not knowing the Winter Solstice is the way of the world, Adam is afraid this is the death God told him about. As the day get shorter and shorter, Adam and Eve begin fasting in repentance. After the Solstice, the days begin to get longer. Adam gives sacrifices in thanksgiving. He  made those days around the solstice into holidays.  People since then have always marked those days with feasting, some in holiness, some in idolatry. The important part of this is darkness. This year especially so. The Jewish Calendar is a Lunar calendar adjusted for the seasons.  It means this holiday season has very little sun and very little moon — it is the darkest of the dark.  That’s why it is all lights festivals. The star of Bethelem, Christmas trees, Menorahs, and Yule logs are about light cutting through the darkness. They are all metaphors for the same thing: In times of spiritual and mental darkness, we must be the light cutting though the darkness, enlightening ourselves and others. I go into this in a religious context a lot more in the one fable I’ve ever published on Kindle, The Tzaddik of Klaas. My first publishing effort, the Tzaddik of Klaas. It’s a bit of a Christmas origin tale, jewish folk tale and interfaith philosophical discussion. It’s one of the best writing I’ve ever done. But I want to look at this in terms of the creative indie, more than religion. Darkness is around us in many ways. Creativity and the creative chases away the darkness. The greatest creative act ever wether you believe the Bible or the Big Bang was “let there be light.” We can enlighten, we can delight. Contrary to its detractors, Apple has rarely invented anything. They just took what was there and made it a delight. We can make our creative work a game that makes a bad day better, a course or book that makes a frustrating  problem simpler, or an app that gets a tedious job done. All can bring light into the world. All can have a user interface that makes intuitive  sense to our user, helping them do what they need to do. Your code can make the world a brighter place. As I’ve spoken to may of you, I’ve learned you have knowledge and wisdom beyond code. Many of your projects are about your expertise translated into code for a mobile device. It may not be your programming as much as your content that bring joy and delight to your customers. Whatever you celebrate this solstice, may you find joy and light. May you bring Joy and light to those around you. Remember all year round, the  joy and light your work brings is like the candles on those menorahs or candelabras. One candle can light many, but never lose its own light. Happy Holidays and Keep coding, Steve

    5 min
  3. 12/05/2016

    #36 - How Your Project is Like the Best Sandwich I Ever Had

    Hello folks! I’ll start again with the business stuff then work into my commentary for the week. If you didn't se it yet, I did post last week about the new Update Frames button in Xcode 8.1. I'm trying to finish four Lynda.com courses at the same time, so I'll try to get to fix it in the books soon as I can, but I'm swamped. You'll find the article also on the Book's webpage The new lesson is up on the website. This week I’m showing you how to use actions and categories with your notifications. This is a cool way to execute bits of code directly from the notification without opening the app. For the tip of the week, I found out that the newer simulators work just like their device counterparts. That means any use of 3d touch in a simulator requires you to have a 3D touch trackpad. If you don’t have a 3D touch trackpad, you can't do all functions  on iPhone 6s, 6s plus, 7 and 7 plus simulators. As I’ll describe in the post, this has some serious repercussions, since the newer phones require a 3d tap to get the actions displayed. The workaround is to use an iPhone 6 or 6 plus to test notifications or other application using 3D touch in the API's. This would be the latest phone without the 3D touch feature. I have a new idea for this newsletter that I’m beginning to work on. I have two readers who were nice enough to send me their apps to look at. Both apps I like a lot, and I’m thinking they might be cool to review and constructively critique on the newsletter. I haven't gotten permission from either person yet, so If I do this, it will start next week. If you are interested in submitting an app in the app store for review, send me a valid redemption code  at podcasts@makeapppie.com with some info about you and your app and I’ll take a look. Some of you might remember last week I promised to tell you about the second best memopry from my trip to Russia. That memory actually happened not in Russia but in Helsinki, on a stopover, but  on my way home.  It turns out I heard some news last week that dovetails into that story. Restaurateur Jim Delligatti died last week at the ripe old age of 98. You might not know that name, but I’m betting most of you know of his innovation, one that the corporate environment he belonged to resisted. Delligatti knew  it would be a hit, because he listened to his customers more than corporate. His innovation is known world wide. While he lived in Pennsylvania, it was in Helsinki that I found his invention was the best sandwich I ever tasted. In August of 1986, a few months before I went to Russia, the Chernobyl disaster happened. It changed our trip, cancelling the original stop of Kiev since getting there would require going dangerously close to the affected area. It changed the name of our dinner and lunch too. No longer was it called Chicken Kiev. It was Chernobyl Chicken.  Lunch and dinner every day for two weeks was Chernobyl Chicken. Even the ultra hot mustard condiment was not enough to make this tasty by the end of the trip.  After two weeks, I never wanted to see a butter stuffed breaded chicken breast again. On our way back from the Soviet Union, we had an overnight layover in Helsinki. Many of my class mates and I went across the road from our hotel, to a restaurant there. I think we all ordered the same sandwich. The two all beef patties, special sauce, lettuce, cheese, pickles, onions on a sesame seed bun I ordered with fries and a Coke was the best sandwich I ever ate. Yeah it was a Big Mac. That was Jim Delligati’s invention. There’s a lot to unpack there. How could a fast food icon be the best sandwich I ever tasted?  I mean, I’m pretty much a foodie. Most of you know me how I obsess about pizza. But I love food. I remember the best risotto I ever had was at Ristorante Mario’s,  just behind the forum of Augustus in Rome. The best coffee is Ladro's in Seattle or any coffee shop brewing 100% Kona on the Big Island of Hawaii. The best crepes are in the tiny town of Galesburg Illinois, at a place called the Landmark. The best pizza in the world is Pizza Renaldi in Cozumel, Mexico, washed down with a Limonada. I’ve been to restaurants worldwide. One star to five star. Why would a Big Mac be my favorite sandwich ever? To be clear it was that Big Mac. Three weeks a later, the Big Mac at the local McDonalds I could take or leave. Food carries emotional value. That Big Mac in Helsinki was coming back to civilization. It was coming back to frredom and to the west. After all that Chernobyl chicken, that Big Mac tasted good. That's known as contrast bias. When exposed to something that we don't like, especially after repeated exposure, there is a relief when we can change. Robert Cialdini in his book Influence gives the example of real estate brokers who show two or three really bad houses before showing a mediocre quality or a house slightly over the budget of a buyer. They people looking at homes like, and may even buy, this house not because it is the best for them, but it is not one of those objectionable houses.  I liked a Big Mac in that moment because it was not Chicken Kiev. It could have been any food that wasn't Chicken Kiev and I would have loved it. That's one marketing strategy you might take if you are competing with similar apps in the app store. What makes you app different? What makes your app special, or a breath of fresh air in a crowded market? Marketing and user Experience go hand in hand here. By including what is a relief to users in your application, you make your app more attractive to users. Suppose you could build a perfect Pokemon Go clone, complete with proper licensing. Then you go and include the missing tracking feature that users are screaming about in Niantic's version . The users would beat a path to your door. Niantic know this by the way, and spends more time blocking developers from building the missing tracker than actually making better game play. The second thing about the Big Mac is the meaning of a Big Mac. It's not Russian in any way: It's a product of the West and specifically America, of my Home. We map a lot of meaning on things. Often we do not even know how much meaning we map on objects. I mapped a lot of meanings about the warmth of home,  about the freedoms I have at home onto a sandwich. I may have been in Finland, but eating a McDonald's sandwich was mentally coming home. Remember that there are such mappings. Some you can create with enough media exposure. Most you don't, but knowing what those mappings are you can exploit them — or avoid them. Some mappings are negative and will hurt your chances in the marketplace. That same McDonalds Big Mac in France often gets a very different reaction: It's repugnant. Use the one that attract, and avoid the ones that repel customers. And like Jim Delligati, know your customers. Listen to them. Finally, I want to talk about one more story I read about Jim Delligati. Delligati was selling the Big Mac only in his stores. McDonalds Corporate hated the idea of a Big Mac. They wanted no changes to their already consistent menu. They hated having to buy a different kind of bun, one with sesame seeds. This wasn't a radical change by any means.  Such sandwiches existed at other fast food restaurants. “This wasn’t like discovering the lightbulb,” he told the Los Angeles Times in 1993. “The bulb was already there. All I did was screw it in the socket.”  But there was still corporate resistance. What changed McDonald's mind about the sandwich, and eventually led to it becoming one of the most profitable items on the menu was local growth. After Delligatti introduced the sandwich in his own stores, neighboring McDonalds owners  Started carrying it too. Corporate had a different option when the sandwich successfully spread like wildfire across Pennsylvania. Always remember that your project is like a big mac. It may not be something radically different, but it can have some impact on people. Listen to your users to find what they want.   No big guy might want it, but let it spread locally first before taking the world by storm. It may have mappings of feelings and memories of good things. Exploit that for the local population first, the rest may follow.  It may be a breath of fresh air in an otherwise oppressive environment, making it amazingly attractive. I hope your apps sell like big macs. Keep coding, Steve

    9 min
  4. 11/28/2016

    #35 What I Learned in the Old Soviet Union

    Hello All, Just a little bit of business this week and then on to some thoughts for the week. This week's post is inspired by correspondence I've had with Denny, one of the subscribers to this list. It's the basics of using gestures in your own applications, where I'll cover taps, pinches and rotations. 

I also had a lot of problems with Xcode this week. First the beta iOS on my phone won't work with the non beta Xcode I was using. Then the latest beta wouldn't work. Kept getting a cryptic error message in the build. Turns out that a lot of fatal errors that have cryptic error messages when using devices occur due to corrupted or invalid provisioning profiles. Took me till Friday to clear the problem and get real work done this week. I've gotten a lot of ideas from people writing me this week for posts. Someone from Twitter wants me to follow up my notification posts with one on Notification actions, which will be next week. Updating Frames in Autolayout For those of you about to tear your hair out about auto layout, Apple made a change that makes me want to scream. They changed where Update Frames is, deleting the original selections in the resolver. You'll find it as an icon next to the left of the stack view icon.  Why they had to delete it from the resolver, I have no idea. What it means is  I have another round of revisions to Practical auto layout to do that I don't have time for. I'll have an errata in the website about it shortly. Thoughts for the Week I'll end the post this week with some more thoughts. Due to some letters I received last week, and a movie I saw over the weekend, I want to relate some memories from a long time ago. When I was in college I spend a mini-semester touring the Soviet Union for a very cold, dark December, but one that was very enlightening. I had some interesting adventures like getting interrogated by the KGB if I had any contraband. Besides being patted down and having them try to see if I had a false compartment in my boots nothing else exciting happened.  Then there was tour bus leaving without me and my roommate at the Moscow Circus. We made it back to our hotel using the Moscow metro with no problem. But that's not the two memories I remember most. I had an idea that started jelling a few days into the trip, and kept getting stronger as the  trip continued. As foreign nationals we were  almost always escorted everywhere by the Soviet tourist agency Intourist and of course given the party line about everything. I stopped counting the times our guide mentioned that Russia got invaded by some other nation — until I saw the bullet holes in Leningrad, now St Petersburg. Bullet holes were in buildings everywhere, from when the Nazis tried to capture the city. There were still bombed out buildings in the outskirts of the city from World War Two. On the plane home, after my second best memory of that trip (I'll talk about that next week) I formulated my trip in a very simple idea.  There's people who risk and people who want to be safe. As a large social unit, the People of the Soviet Union, and I suspect still much of Russia today, want to be safe more than anything else. On the other hand,  there are those who want to risk to become better, are willing to work hard, and willing to get very uncomfortable just to grow and succeed. In 1986, I believed that was what forged the United States and made it great. The U.S.  with two exceptions is an immigrant nation. People risked everything to come to America. These people worked hard and innovated hard to succeed, and the incredible growth of the U.S. Has that in its DNA.  That was my idea at the time. It gave me great framework to understand the true cultural clash of the USA and the USSR, why we both spent so much money pointing missiles at each other during the Cold War. One wanted to be safe, one was all about risk and success. In the decades since then, I made a few changes to this. One that got reinforced big time in the last few weeks is the idea that as one moves from the initial immigrant generation, risk changes to safety. To be protected and acknowledged as part of society becomes more and more seductive. What form that safety takes changes, but it is there. Not just in America, but around the world this idea of being safe above all else is growing. Over the Weekend I saw Disney's new movie Moana. It is at its core, a Hero's Journey movie. The hero's journey is a pattern that shows up worldwide in Myth. Its the story of a person taking a fantastic journey and become something new by the end of it, often saving everyone else by their actions. The first Star Wars movie was a hero's journey.  Farm Boy Luke Sywalker goes through a series of adventures and trials ending up making the shot that destroys the death star. My other favorite Disney movie Mulan, is a similar hero's journey of a girl who's supposed to get married, but ends up running away to enlist in the army and ends up almost singlehandedly wiping out an invading army. Moana was like that, but without much in spoilers her choice was to stay safe on her island or risk death outside it. Turns out if Luke, Mulan or Moana hadn't  taken that risk,  everything would have died. That's one of the core ideas of the Hero's journey. To stay safe is guaranteed death. That brings me back to those risk-loving hard working types, who think by their own hand they can bring success. Creative indies are among these, willing to try something new, burning the midnight oil, or in my case getting up at 3:00 in the morning. These are the people who work 20 hour days to improve their lot. They come up with the most amazing things. Apple's classic commercial, and one of my favorite quotes sums them best. Here's to the crazy ones. The misfits. The rebels. The troublemakers. The round pegs in the square holes. The ones who see things differently. They're not fond of rules. And they have no respect for the status quo. You can quote them, disagree with them, glorify or vilify them. About the only thing you can't do is ignore them. Because they change things. They push the human race forward. And while some may see them as the crazy ones, we see genius. Because the people who are crazy enough to think they can change the world, are the ones who do. That's you. Some might call you crazy, I'll call you heroes or creative indies. I'm blessed to have such people as my audience. I've been corresponding with many of you and are blown away with your creativity and grit. More than once last week,  I heard a variation of a phrase "instead of getting depressed I got coding."  For example one reader, Denny, is writing apps to change how electrical contractors do their job.  I just blows me away how innovative and without a doubt revolutionary his work is. I think many of you have similar ideas and dreams, working your way to learning Swift and API's to make your work come true. I wanted to thank all of your for your efforts. Wherever you are, your work matters. You are my heroes. With that said, I can think of only one more thing, which means more to me this week. Keep coding. I'll talk to you again next week.

    8 min
  5. 11/21/2016

    #34 Why I Switched Mail Lists

    Hello Folks, I'm going to start with some follow-up from last week. Last Monday seems almost a century ago, though it was only seven days. I was upset and very depressed last week.  I was also honest, a little more honest than some on this list wanted.  In retrospect the damage isn't bad. I got only one really nasty note about that post, who I unsubscribed and five people who unsubscribed either complaining that post was inappropriate or my politics didn't belong in their feed. I assure you that is my last truly political post.  The post was more about my feelings than anything else. With that said I will make clear that A Slice of App Pie is my site and I will say and do exactly what I want here. If you believe that you are in any way superior to any other human being because of your gender, who you choose to love, the color of your skin or your religion,  please unsubscribe. I will not be political, but much of what I have to say about being a creative indie assumes we are all equal but have cultural differences. I don't call that political — that's who I am. You won't be comfortable with what I am going to say if you cannot accept that. Okay enough of that. Onto the first topic of the week  which is still related to last week's post. Those six people give us a really cool opportunity for you to understand why I moved the e-mail list. That explanation was supposed to be last weeks post - why I made the move from Tinyletter to Mail Chimp. While I like Mail Chimp, this applies to other similar e-mail list system such as Constant Contact. Higher end mail systems have nicer content creation tools, and the look of the newsletter plus the speed I'm able to produce it are very important to that decision. The second reason I moved is metrics. Tinyletter had almost no metrics. On tiny letter, I know only that a little less than third of the newsletters got opened. Beyond that I know nothing. Mail Chimp is a different creature. I know a lot about you, more than you can imagine. One example is the location you subscribed from. I can assume a lot about you from that information, and even group you regionally. Our six wayward friends, between their exit comments when they unsubscribed and their location lets me makes some simple inferences. While I have street addresses, for our purposes all you need to know is they were from Georgia, Western Washington State, Texas and Kansas. Given the political outlook in those geographic regions their unsubscribing makes total sense, and I wish them well. That's the example I wanted to share with you of using analytics to understand something that happens to a list. Unfortunately I don't have any interesting data on iTunes connect for an example. The analytics is getting better there, but they aren't as granular as this — at least for us.  Apple doesn't give exact locations for a download, only countries. I'd love to see for my apps where people are downloading them. Geographic data can tell you a lot, as tribes do form in geographical regions. These are people with shared cultural values. If you have access to the cultural values or other demographic data that you can assume cultural values from, you can understand an audience better. That's really what I'm doing with Mail Chimp. I'm looking at who you are, and then I can write what might be the best articles. Not everyone will agree or like what I write, but I know who I am writing to better. Some of you, rightly so, should be getting chills. The first time I opened Mail Chimp's analytics, I got them too. Even when you don't volunteer information, you are giving a lot more than you imagine. Most e-mail systems do this to get the best idea of who their audience is. My ethics is such that while I will reference this data, I will not mention specific data about anyone. I will, however talk vaguely and most often with aggregate data. Your data is safe with me. As another example, Location aggregate data is one of the patterns I have seen repeatedly on all my sites. Although this is written in English, this is not a purely American site. Americans may be the biggest demographic, but they are by no means a majority. Only 42% comes from America, 58% are outside the U.S. I need to think about that too, and what it really means, because I really don't know what to do with a global audience, with lots of different assumptions and cultures behind them. In some of these newsletters I'll talk more about the analytics. I think it is especially important for us to understand them to discover our customers. As I discover things over the next few months, I'll be writing to you about them. Mail Chimp is a new adventure in marketing for me, and I hope I can give you insights about e-mail lists in this experiment. Let switch over to iOS. I got a lot planned for you in the coming months. There are several topics that are tickling my fancy, not the least of which is something that came out of the lynda.com course. I wrote a whole chapter about notification on the Apple watch for that video course, but along the way found out that the new UserNotification framework has some pretty powerful  stuff in it. And so, I'm a bit hooked. This week post  goes into the management of local notifications. A fan wrote me about a problem he was having, and this happened to dovetail quite well with his problem. You'll learn a lot about local notifications there.  I'll add one more thing here that I did not cover there. While you all have seen notifications on your phone, you may not know how the new UserNotification  framework does it thing. I'll go more into detail in the posts on the website if you want code. You as a developer add a notification request using a UNNotificationRequest Object. This object has three parts: an identifier, a trigger and content. While you can assign values before you add a notification to the notification center, once you do the request becomes read only. That the one thing I left out of the lesson this week. If you want to change content you make completely new request and then replace the current request with the same request identifier. You can only replace not change a request. Now for my progress news.  Swift Swift View Controllers got delayed again, due to another round of Lynda.com courses. I'm also running into a big stumbling block of Apple shutting down publishing services for a good chunk of December, so it make it difficult to get everything done. I'm targeting very early January to get the thing complete. But I'm going to try an exploratory update over Thanksgiving. So some changes are coming soon. Speaking of Lynda.com thank you for those of you who took a look at least the demos from the WatchOS course if not the entire program.  For those of you who heard my earlier episode of selling out and selling it I hit a gray area with this. I said in that post That I have a huge problem with affiliate programs. However, there is a Lynda.com affiliate program and I'm not sure if that is selling out or selling it to set the Lynda.com affiliate program up. I'm still debating it with myself. It would be to sell my product and make more money from it, but I'm not 100% certain of that. If you have a thought, let me know. Practical Autolayout seems to be doing well on both iBooks and Kindle. Thank you all for your purchases. So that's it for this week's post. Hope you have a good week. If you are that 42% of the list from the U.S. Have a Happy Thanksgiving. I'll be talking to you next week, so keep coding.

    9 min
  6. 11/07/2016

    #33:A Banana Bunch of New Releases

    Hello all, As promised, This will be a longer one. A lot going on here, Some of which you already know. We have a lot of book news, and I can finally tell you about the Lynda.com course. First the tip of the week. With Practical Autolayout now released, I'm going to talk about Apple's bizarre way of writing constraints. One thing I cover in the book is reading constraints directly in the document outline. For constraints that are relations between two views, there is a folder in the document outline that contains all of them. Suppose you have two buttons labeled Banana and Hot Fudge. They are spaced horizontally apart 10 points and pinned to the top and later margin. Click open the constraints in the document you see they are written as algebra equations. One equation in the set there would be: Hot Fudge.leading = Banana.trailing + 10. These equations default to plus, never minus. That equation tells you that there is spacing of 10 points between the Hot fudge leading edge and the trailing edge of Banana. If you see a minus, that means someone manually reversed the constraints. If it is flush with the margin, there would also be a constraint of Banana.leading = leadingMargin, meaning the leading edge of Banana is on the leading margin. It doesn't not say +0 in those cases, it just leaves it off. An alignment can also be a equivalence. Both buttons when top aligned would have a equation of Banana.top = Hot Fudge.top. If you know how to read these in the document outline, you can pick out constraints directly there, for modification or deletion. It's a good skill to add, and speeds up selecting constraints. I go into this more in Practical Autolayout for Xcode 8, and where it is particularly useful. Speaking of Practical Autolayout, its out and I'm starting to see sales. I'm going to assume that the first nine iBooks sales and eight Kindle sales for the Xcode 8 version I got are from my readers on the email list. Thank you for those sales. Hopefully I'll be able to increase those sales over the next few weeks. For this list there an elephant still in the room I'm going to talk about right now: updates. If you read my post late last week announcing the book, I told you the bad news: I made too many changes to the structure of the iBook to be an update of the previous book, and therefore had to issue a completely new edition. I did get a good question about this last week: If you have to buy a new book, which device should you pick? I have two answers for you: The first is the one you find most comfortable reading. The Kindle edition has the dynamic fonts so you can change the font and font size of the text. The iBooks version is static, but has been carefully formatted to fit the page Here's examples of the same page in both formats. If you are listening to this on the podcast, you can check the show notes for the images. Kindle Version IBooks Version Whatever device you like is great — in one perspective any book you buy is good for me. On the other hand, I do make more from the sale of an iBook at a 70% royalty than a Kindle version at 35%, so I'm kinda biased towards iBooks, where I can at least correct typos and update to everybody the corrections. You can also download free sample chapters on both platforms if you want to try them out. You can find more on the iBooks version here and the Kindle version here. If you are listening to the podcast I left the links in the transcript. There's another elephant in the room too: updating Swift Swift View controllers. I have no idea what's going to happen there. I was already planning for a update incrementally, and that might just get me past the filters that look for big structural changes. My current plan is to get the draft I have updated to the book this week, which will be the Xcode 8 and Swift 3.0 changes for chapters 1,2, and chapter 4 section 1. If that loads without problems I'll update the code for the rest of 4(modal view controllers), then go back and update what images I'll need to update. I'll then do the same thing with chapters 5(embedded view controllers) and 6(delegate view controllers) While slow, hopefully that will keep me merely in update mode for most of these chapters, and you will have correct code for Swift 3. I'll tackle the big problem, Chapter 3 last. Chapter 3 is the auto layout and size classes chapter. There's no way to get around deleting a section there, so it may not work. But if all goes according to plan, all of you with Xcode 7 copies of the book will have one last major update before I have to mothball it next year for a new edition. That's it for books right now. You If you have questions you can e-mail me at podcasts@makeapppie.com or just reply to this newsletter. Not to the other big announcement of last week. Lynda.com released on Thursday my first video course Learning Apple watchOS3 App Development. If you know a little bit of Swift, I'll guide you through how to make apps for the the Apple Watch. It's a market that hasn't reached its full potential yet, and with a lot of the new additions to watchOS 3, watch development looks very promising. I'll go through most of the objects you can add to a watch face, how to use navigation on the watch, and how to use some important functions to the watch like complications for fast access to apps, and notifications. In the newsletter and show transcript, you'll find a sample video if you'd like to learn more. Learning Apple watchOS 3 App Development by Steven Lipton I'm very excited about this video course. Lynda.com is a subscription service, so you'll need a subscription to watch the whole video. If you have a LinkedIn profile and a premium account, check the features for that account. Some levels have access to Lynda.com courses. I'm setting up some other ways to subscribe, and hopefully those will be in place shortly. This course is only the beginning. There are more in the planning stages, and again I won't say more than some are iPhone and some watchOS. Once they are out, I'll give you more information about them. The post this week, is a preview of the Practical Autolayout book. I've posted the updated Chapter 2. You can get that chapter as part of the free samples on the iTunes and Kindle as well. Have a great week, I'll be talking to you Keep Coding Steve

    7 min

About

The Newsletter for Creative Indies