do the motion meetup just about every month, sometimes less. And we have a good old time, and I've been fortunate enough to be asked to help lead the panel today. We have some amazing people. The category is Ruby Motion in Production. So if you have any questions about your particular apps in production, we have a great set of people here. We have Ryan Rominchuk from Frontback. We have Daniel Dickerson from Bandcamp. And this guy, nobody knows who he is, Colin Gray, everybody. So we have Colin Gray, and he's going to be representing Jukely today. And so we have some questions. Now, the great part about this is that you guys get to come up and ask your questions as well. We're going to go ahead and seed some questions to start it off. But if you have a question, please line up right over there on the left side. We'll form a line, or any way you want to. And we'll divide the questions out to you as we see fit, which means if Todd comes up here, we'll ignore him. It's fun to dig on Todd Day. All right, guys. So what I'd like to do is I'd like for each of you to introduce yourselves formally. Talk a little bit about your app so that everybody knows we might not have used each of these applications. So if you don't mind. Colin Gray, and I am the community manager at Hip-Bite. When that role comes up, it's kind of ad hoc and here and there. My full-time job is at Jukely. It's a startup based in New York City. We've built a music application and music promotion platform. So we link up local live shows with people who love music. And hopefully we give them music that they're interested in. I think the tagline is it's like a mixtape made by your stalker. So we really try to use your, re-aggregate, Facebook information, SoundCloud, let's see, your iTunes music, lots of different music sources, Spotify, RDO. We take all those likes and favorites, put them in our algorithm, and then deliver recommendations back to you. Hello, I'm Daniel Dickison. I work for Bandcamp, which is music, a lot of music, I guess, online service for artists to sell music, digital music online. And the app, the first version of the app, was basically a way to listen to your purchased music on the go. And since then, we've been slowly adding more discovery features. You can follow artists and other fans and see what they're listening to, see what they're buying, and check it out. So the Bandcamp app. And yep. Yeah, I know. Hi, I'm Ryan Romachuk. I'm an iOS developer at Frontback. And we are a photo sharing app that is you and what you see, much like the name suggests. You're able to take two photos with both camera devices, or two fronts, or two backs, and two photos on top of each other. Excellent. All right, so I'm going to go ahead and start with the first question here. Basically, a start. What made you choose your production app to be in ruby motion over any other possibility that was out there? Yeah, so the origin story of Frontback is interesting. I was in Russia for the last two years, doing iOS Objective-C app for a company that are called Osterok.ru. And Frontback is basically another company, a consumer web company called Check This. And they basically were out of money. They were Rails developers. And they started working on a fun little app, which is now today's Frontback. If it wasn't for ruby motion, Frontback would not be where it is today. So I was able to really save that company. Nice. Yeah, so I had done, personally, I had done some Objective-C and iOS development before. But the rest of the band camp guys are all familiar with ruby. So that was really the driving reason for using ruby motion to write the app. Michael Bieber, who's over there, he's another band camper. But so he was able to come on to the iOS project sort of after the initial release and just kind of get up to speed real quickly, because a lot of the code is just straight ruby. So that's the big reason. So I'll answer this in two ways, because I came on to the app later. Bora Selleck is the creator of the app and founder of Jukely. And he chose it because he had had a long history of Java and before that, Microsoft development. And he knew that he wanted to do a startup. He wanted to do an iOS app. He had a Jukely idea. Him and one of the original Kickstarter designers, Andrew Cornet, got together. Cornet, Cornet. I hope he doesn't watch this. And they chose ruby motion because, again, of the ability to write in ruby, he wanted to enjoy this startup that he was creating. So he created the app. It took him about three months to release the first version. Then they contacted me because of my activity in ruby motion, asked me to help them out with some bugs. And I said, well, I'm actually already working full time in other capacities. And about six months later, he said, OK, how about an offer? And at that time I was like, OK, yeah. I would love to do ruby motion full time. Nice. Yeah, all right. So to dig a little bit deeper, let's go a little bit further. And now we know a bit about it. Which gems and coca pods are you using in these production apps? Well, we care. So actually, in Jukely, I inherited the app. And so they weren't using many gems at all at that time. I brought in Sugar Cube because I don't know how to write iOS code. I just write Sugar Cube. So of course, I'm the maintainer of Sugar Cube. So there's that inside Juke. They do use a lot of coca pods, AF networking. I'm not going to remember them all. Reachability, Mixpanel. I've played with Firebase for remote logging. Gosh, I'd have to pull up my rake file. I don't keep things in memory very long. And let's see here. As we've developed, I've brought in a lot more gems. So I am starting to build the UI and motion kit now. And I think that's the majority of them. Oh, and bubble wrap. Yeah, we also didn't use a whole lot of gems in libraries. Well, part of it was we started development pretty early on and wasn't clear at the time which gems would become sort of stable and a long-term thing. But we wrote a lot of utility stuff in-house also. Some utility things to do auto layout, constraints, and things like that. But yeah, we do use some libraries, just pulling in source files from GitHub and putting it in the vendors directory, kind of old school way, like FMDB if we're doing SQLite accesses. I think we use TMDiscash, which is, I think, Tumblr's caching library, and a few other ones, reachability. I mean, reachability's everyone uses that. Yeah, so yeah, but even now we don't have a whole lot of gems pulled in, which I think probably will change after learning about a lot of the libraries here, so we'll see. Yeah, we use very few. We use, basically, we cherry pick the things that we really need. So like CherQ, we cherry pick the localization. Bubble wrap are using just the location. It just makes it a little bit cleaner. The only DSL we're using is Clay's AFMotion for AF Networking, which makes it much nicer. We're using SDU Web Image for our image caching. Yeah, yeah, yeah, it's amazing. AF Networking, the usual suspects, but that's about it. Gotcha. Excellent, so as far as all the different setups, what's the exact business model? I'm especially interested with Frontback and some of these other items. What's the idea here? You're going after the user base. What's the financial roadmap? Well, I mean, the photo sharing space is huge risk. The only way to win is to win the entire market, so it's all or nothing. It's like we're not, you know, we're gonna kill Instagram or not, and AFMotion's gonna hopefully help us get there. Yeah, for us, I guess we already had a established business, sort of, so it is a little bit unfortunate that we can't sell music directly through the app because of the Apple restriction. But yeah, people go on the web to buy the music and then just have a new way to listen to it easily without having to import music through iTunes, which is the pain of the butt, so that's just adding extra usability, really. So yeah, in Jukely, we have a couple revenue streams. We sell tickets through the app, so it is you're scrolling along, you've gotten a recommendation, you open that up, you can listen to it on the app, and it does a fun thing if you let it just play from person to person. We use the speech synthesizer to say the artist's name and the date, so you can hear beforehand, oh, I dig this, and you can open it up by the ticket right there in the app. And then the other part is the marketing aspect, so we are bringing artists to customers. I think there's value in that, and so we get some, actually I don't know how much I'm allowed to say about that, but that is, obviously there's revenue to be made from that. Very nice. And so actually, I see we had an audience question from a gentleman who's gonna be talking about marketing today, Mark Rickert. Hey guys, so I know when you have an app in production, things don't always go the way that they went on your simulator or on your device, and so there's inevitably problems that rear their ugly head in production. Can you guys talk about how you handle those things, maybe services you use? I know you mentioned Mixpanel for analytics, but what about crashes in production? How do you guys track those and handle those errors? So yeah, we also use Hockey App, and I highly recommend Hockey App. There's lots of bug reporting tools, and I've actually had some success with, as far as setting up, I've set up Test Flight and Criticism and Hockey App. I like all three. We're using Hockey App, and it's working very well for us. We also use, yeah, I actually use kind of three logging, so Hockey App on a crash, Mixpanel for user interaction and user behavior, and then I also use only in development, I use Firebase to send logging events, and it's very verbose, so it's like this streaming log of every request and kind of everything. So that's my noisy developer log, but let's see. Also, a lot of fixes have happened by having an API that is catering to iOS. What I mean is our API is obviously consumed by the web service as well, but we can change the web service very quickly. So if we find out that data is being expected on iPhone and that's not coming from the API, we'll rework the API to accommodate that and then rework the web service to accommodate that just because we can do those two things instantly. You can go really far down that road to, I've heard of people having all their UI serve from the web, so you have a version on the device, but then it can get refreshes from servers. That seems like some voodoo to me, but it can be done. Yeah, crash reporting is a good one, because in theory, you can go to iTunes Connect and you can see crash reports there, but most crashes don't actually show up, so we ended up just using a PL Crash Reporter, which is just a client-side thing that dumps out a crash log locally and then we just upload it to our server on the next launch and we track it that way, which is, it's okay, it's kind of a pain to symbolicate after the fact, but at least we do get a sense of the frequency of the crashing and there's definitely things that crash only very infrequently, like especially with concurrency-related things, so it's good to actually get a hard count of the number of crashes that are happening, which you just won't see in beta testing. Yeah, and also for general event logging, again, we kind of queue them up on the app and then send them to our server, where we have, we already had various ways we're tracking stats on the site, so we kind of tie into that, have a new stream of data that's coming in just directly. Yeah, pretty much a lot of the same. We have a large, dedicated beta testing group on Hockey app through our enterprise certificate, so we try to get hundreds and hundreds of people downloading and catch the crashes on Hockey app. For non, for events that I want to know about that aren't, I don't want to cause a crash, I send to Google Analytics, because our mixed panel bill is already way too high. The other tricky thing is, when you build a binary for Apple with your app store certificate, you actually never get to run that binary on your own device, so there are actually, you can really mess up and wrap some code around a production if block and not realize that, have a bug in that section, so the best thing I do now is under the notes is to say, sometimes Apple will not test your app, so I say, please make sure the app launches. And so that, that goes a long ways actually sometimes. I might have to quote you on that. So there's a constant RubyMotion underscore in and you can have this kind of fork of code, so for instance my Firebase logging only happens in development, so that's Hockey app simulator and on device when I compile it. Anything in production doesn't go there, so yeah, if that's the other if block, you will never run that. You could compile your app for release, so mode, rake, mode equal release, and that'll compile it for production. It actually leads me into a really good statement. I have some insider trading information on you here, I know one of the problems that I think people come across is that you'll have an app with more than one developer working on it and then you'll have the issues, like how do you handle that? I know specifically use a motion M, is that the gem or do you just set up in your environment? No, I do in the rake file. I should use motion M or something, but again this is a situation where I kind of came on and fixed what I needed to do what I wanted, so what I do in my rake file, so there's three people who, actually four people now who will compile the app, most of the time it's me, I'm the iOS developer, but also the two founders and then also our API guy, so they'll compile it and for each of them, basically I check the end user and if it's Bora then I do the settings for Bora and he can change those, if it's Andrew I do it for him and then we have another version for Hockey App and another version for release, so if it's in release mode it goes down there. So yeah, if you need to enable and disable things for you or for certain testers, things like that, so for instance you could do A-B testing, there's a fun trick where you can go in your rake file, check for those settings, so this is during compile time and then include a Ruby file, either this one for one, kind of like an A-B testing, or you might generate a Constance file and include that at compile time, and we do both of those. Another way you could do it also is in the rake file you could set arbitrary keys in the info P list and then you can pull that out at runtime, so I think we do that for enabling test flight, SDK stuff for test flight builds, but I think we try to keep the test flight builds as close to the production release settings as possible, so try to minimize things that are, just come out for the release build. Also, if you're working on a team, I strongly recommend you actually version your Ruby motion, so like if you have a new hire, he could download the latest head when you're working on another version, and that can cause a lot of issues, so I check in, if I'm running 2.28, I check it in and everyone is forced to download and cache that version of Ruby motion. Nice. You can specify a version at the top, I'm just loud so this thing doesn't actually affect my, and that reminded me of another thing and I'm gonna forget it. Oh, tag your releases, so when you put out version 2.1.1, tag 2.1.1 because in your stack traces sometimes they won't symbolicate right, and you'll just get all these memory addresses, and if you try really hard, you can symbolicate them on your machine. You can go, you can compile it for production, you can find that address, and you can use A2S to get that line number, it's not easy, it's not enjoyable, but it's possible, and with some of these crashes it'll save you, but you must tag that release, any small change, and all those memory addresses are just all different. Gotcha, all right, it looks like we should take another audience. How do you guys do your builds? So how frequently do you release a production build to the app store, and when you do that do you build it just by hand, or do you have that automated in any way? He's thinking. Well, I mean like we have, so I love to deploy bugs into production, like co-founder doesn't, so Hockey app is great for me because I'm pushing, if you have an enterprise certificate and you have users testing it, and who are always testing it, you can basically get a build out, I mean sometimes I'll have a build five times a day, it'll be fix, oh sorry, fix, oh sorry, fix, which, and then we just basically stay consistent, so if I'm doing the app store build, I'll do the app store build the next time as well, I mean we have, there are those issues where configuration problems, but you can usually have a pretty clean rake file across environments, but it's just, it's more superstition than anything. I'd say for release builds, you know we'll have a release with features that you know that might take weeks or months to do, and then often right after the release we'll find some bugs, so they'll be within the course of a few days, we'll submit another bug fix, but yeah for testing builds, yeah usually we try not to do more than one a day, maybe a couple a day, because I think you get tester fatigue, so yeah but for release builds, it's basically as soon as, if it's a bug fix build, you just submit it as soon as possible and just hope it gets reviewed quickly. Yeah and there is a possibility that you can ask Apple to rush a build, that you won't do it very much, so you can't abuse that feature, but if it is something that's like all your app, it's on the app store and if you open it, it immediately crashes, you can ask them to really please rush this, and sometimes they will or won't honor that, especially if you just ask them before that, then they're more likely to ignore you. So yeah for builds, we also, I do all the code and I never submit to the Apple store, I'm not allowed anymore, for the same reason. So yeah, I build, I send it out, testing happens and then that, Bora will submit it to the app store. Use Hockey app, do have testing, oh we have a checklist that I resend and that's like me being a jerk, like whoever is testing, I want a star by all of these, I did open settings, I did do a filter, I did close it and verify that it did filter, things like that, that we've broken that before, we've broken that before, we've broken that before, so every time we break something, it gets added to the list or of course hopefully we've added things preemptively, and that checklist has helped us a lot, I think that's our earlier best bug fixer. How big a to-do list kind of guy anyway. So I wanted to ask, besides writing tests, which is everybody's favorite part, what was your favorite part of writing the application? The iOS 7 transition, so actually when Laurent showed Jukli, I reeled in horror because that was the iOS 6 version, and our designer is, he's awesome, he is so good and he has such an eye for the iOS 7 mentality of content and context and he just nailed it. If you've used Jukli, you might know what I'm talking about, but it's an iOS 7 look and feel that's just really enjoyable. So it has a lot of custom transitions, custom controller transitions, and those were kind of a joy to code. A lot of blurring and opacity, fade-ins that are just, for me I like to build myself as a UI and UX experience kind of person, and building those out was a lot of fun and I think iOS gives you a lot of really neat tools to accomplish those. Yeah, and didn't it release, iOS 7 was announced right in the middle of all that, and I think that they were announced it and then it released in September, so you got caught right in the mix. We did, yeah, we kind of, we had to, we didn't have to rush iOS 7, we were really glad to do it, you know, Andrew's the designer and he was like, ah, this is gonna be awesome and we had a lot of fun building the designs, but it was also an entire app to update, so just as far as volume, it was quite a rush, but we wrote a lot of helpers, like the nav bar, we rewrote nav bar, so we have our own UI navigation bar like item, but it's all of our own buttons, our own graphics, and it kind of works our way. So yeah. Nav bar's interesting, we have to write our own nav bar too, because the built-in UI navigation bar is really limited in customization, but yeah, and I have to confess, we're pretty bad about writing tests, so we should probably do, I don't know what test, yeah, so that's something we'd probably do more of, but I guess like, favorite part is, when you're working on individual pieces of the code, it can get frustrating, but it's when you see all the pieces finally come together, like you got your server-side APIs working, then you got the client-side stuff working, you buy some music on the site and you launch the app and suddenly it shows up, it's, you know, that's the best part. I'm sure, you know, everyone that writes software can relate to that feeling. And the angels sing. I think one of the great things for me coming to Remotion was, before this I was the iOS developer of Objective-C, so when I first joined, I was like, oh, we're rewriting, we're rewriting, we're rewriting, we have to, but I was actually pleasantly surprised about how compatible becoming, I mean, I was a Rails developer too, extremely compatible, like coming over to Remotion as an iOS developer. At first it's a little like, where's my Xcode tool set, where's my debugger, where's my, I mean, where's my, now you have all of that, those tools, so. Even with like, things like core data, will this even work in Remotion? Everything has worked. Very, almost no problems, so, it was great. Very cool. All right, we're gonna go ahead and do probably our last audience question. Sorry, Todd. He has a back front question, he's working on his own. All right, so, my question is, whenever Hit Fightin' Team releases one of these like 30% increases or something, have you ever been guilty of just, like, bug fix releasing, and just by recompiling, and you're like, ah-ha, we did something cool. We should, it's a great idea. No, I think whenever they happen, actually I'm usually the first one to download it and test it and make sure it works. And I'm always in the middle of something. He doesn't time it for me, for some reason. So yeah, I haven't gotten to do that, but actually, when a Ruby Motion 3.0 comes out, or what version are we on? 3.0, it'll be 3, yeah. With Watson's speed increases, I think that's a great idea. Yeah, I mean, by the time there's a new Ruby Motion bug fix, we have plenty of bug fixes of our own, so there's always something. But it's actually kind of an interesting, with all the speed increases lately, there's one part that we did some profiling in, that we kind of wrote in Objective C, because the Ruby Motion dispatch and string manipulation was just kind of slowing it down, which is the searching through your collection feature, which does some fuzzy matching. So a lot of string operations in a tight loop. So I'd be curious to see, with all these speed increases, if we just go back to the pure Ruby version, maybe it's fast enough now, so it's great that Ruby Motion lets you write Objective C and seamlessly just call out to it. Really trivial to do, which is awesome, but it'll be great if we can just, as much as possible, keep it in the Ruby world. Yeah, and we support over 30 languages, so our language file, our strings are always updating, so I love to have an excuse to get a new version out as soon as possible. And another pro tip is, don't actually write updates in your update field. Write something funny. We have a competition to see how many tweets we can get from our ridiculous staff. I mean, Apple doesn't care. Marketing tip. Very nice. Okay, so it seems we're running out of time, so one of the things I wanna do is I wanna ask one last question with the announcement of Ruby Motion 3 with the BlackBerry support, I mean Android support. What do you see, how do you see this working for your application moving forward? Are you gonna jump straight into using it on the Android side or are you just gonna kind of test it out? What's your plans? Well, unfortunately, we already have the Android version out already, so if this was like a year ago, it would have been awesome. We probably would have been writing the Android app in Ruby Motion 2, but who knows, maybe. I mean, I think we'll definitely play with it, so it'd be interesting to see that. So yeah, I actually had a really hard time because I didn't feel right to tell my coworkers that Android support was coming. I was on strict, no one is told this, so they're asking me, hey, we wanna do an Android app, would you be willing to do that? I'm like, yes? Great, how's your Java? I'm like, okay. Maybe we could use Roboto, and of course, I'm saying we should use Roboto, and I'm knowing it's got the startup time issue, it makes big files, but I don't have to tell them that, but they'll figure it out quickly because of the startup issue, and luckily, at one point, they said, hey, real sorry, but we're gonna have to put that off for many months, and I was like, oh, bummer. So, and then today happened, I'm like, oh, I'm in the clear. Yay, so, Go Team Jukely will be writing our Android app in Ruby Motion. Yeah, we already crossed that bridge. Yeah, we needed Android out, and just bad timing, so we have a great Android developer, we're already down the road, but I'm excited to actually play with it myself. Gotcha. All right, well thank you everybody. I'm sure these gentlemen, let's give them a round of applause to the great gentlemen. I see we didn't get to the end of the questions here, but I'm sure these guys will be around, right? So, thank you everybody.


Hello and welcome to this pre-record of the Monday market webinar on Monday the 26th of January. First and foremost get the formalities out of the way and the disclaimer. And then we can actually get started at looking at the markets and hopefully what to expect from the markets this week. Well first and foremost obviously the item that's front and centre is the Greek collections. And they've been dominating an awful lot of column inches over the past week or so. Largely because of the election of Alexis Tsipras and Sarita as the new government of the austerity affected country. European markets fairly relaxed about it at the moment. Even though this Greek stock market has dropped quite sharply and Greek bond yields are starting to push higher again. The 10-year bond yield is around about 90% at the moment. So there is a little bit of concern on the margins that Sarita is currently on a collision course with the EU. The fact that they've teamed up with the independent Greeks to form a government I think really reinforces the fact that they're more interested in what unites them than what divides them. Because the independent Greeks are very right-wing, Sarita is very left-wing. So they don't really have an awful lot of common ground yet they've chosen to form a government. So markets have been fairly relaxed about it. The Euro has made a new 12-year low but at the moment it's trying to find some element of support around about the 111 level. We did post a low of around about 110-98 but we do appear to be showing some signs of pulling back. So it would appear that for the time being markets are fairly relaxed about what's going on with respect to the events in Greece, even if Greek markets aren't as relaxed as the markets surrounding them. So let's certainly look at the German DAX, the Germany 30, and that's broken higher, quite significantly higher as it happens. And I think there's a good chance we could hit 11,000 on this particular market. And I think what's going to be turbocharging that along with other European markets over the course of the next few days and weeks is, last week's unexpected decision by the European Central Bank to launch a foreblown sovereign bomb buying programme. When I say unexpected, I mean unexpected in the context of a month ago, it still had significantly legal hurdles to overcome. Obviously it overcame them with the ruling of the European Court of Justice, not the ruling, but the advice given by the European Court of Justice that the OMT programme was by and large legal under certain circumstances. And I think in that context that's given the green light I think for equity markets to take advantage of the extra liquidity that will be pumped into the European economy over the course of the next 12 to 18 months to buy equities further. It's obviously had the expected effect on yields in the periphery. We've seen Spanish yields, Italian yields, French yields and German yields hit record lows. So once again you're getting what I would call this flight into equity markets on the back of this liquidity push. Now there are going to be concerns, significant concerns that the demands of the new Greek government put them into direct conflict with the EU. We've already had European politicians coming out this morning and saying that under no circumstances will there be any form of debt restructuring or debt forgiveness or anything like that and that while they would consider lengthening debt maturities or lowering interest rates, other than that Greece must stand by its obligations. So when you actually look at the two parties, their positions, their starting positions are quite divergent and I think that is going to be a significant problem going forward. Who is going to lose face? Now this isn't likely to be resolved overnight. Greece still has to the end of February to come to agreement with respect to its bailout. He's been given a bailout extension until then. So you're certainly going to see an awful lot of rhetoric from both sides, digging heels in and what have you. But I find it hard to imagine that Mr Sipras will be able to give too much ground even if he wanted to for fear of splitting his coalition because his coalition remains extremely fragile given the diverse range of views left and right wing on both sides. As I said earlier, what unites them is the fact that they're both opposed to austerity, they're both opposed to the bailouts and the terms imposed by the bailouts and the troika. So we'll certainly be very interested to see how all of this pans out. In the meantime, the market is understandably focused on that, but it's also focusing on the economic data that we've got coming up later this week. And in Europe particularly we've got the German IFO which came out much better than expected. Certainly there's an awful lot of unease I think in German circles and probably some other northern countries like Holland that the quantitative easing programme is unnecessary. Certainly if you look at German economic data there's certainly an argument for saying that it is. But as Mr Draghi said I think a couple of weeks ago, economic policy is not set for the purposes of one country. It's set for 19 and there in I think lies the problem and the contradiction of the Euro area. So we've got the German IFO that came in better than expected. Also later this week we've got German unemployment data and that's again expected to come in at record lows at 6.5%. German CPI is expected to post a negative number for the Euro Union number at minus 0.1. And I think that's largely why Mr Draghi was able to push through the quantitative easing programme in the way that it was. The decision wasn't unanimous. Expect further noise. Heard a Germany about the legality or otherwise of the QE programme. It doesn't start until March so that does seem to suggest that maybe between now and March we could get some unexpected political surprises and potential legal challenges to the ECB's decision that we saw last week. We conclude on Friday with unemployment data from Italy and again this again highlights the divergence between economic conditions throughout the Euro area. That's expected to come in at 13.5%. Another record high up from 13.4% in November and EU unemployment is expected to remain at 11.5%. Again quite high. CPI numbers for January. Again I think that's going to highlight the fact that the whole highlight the reasons behind the ECB's decision to pump more money into the economy. Year on year EU CPI is expected to come in negative to the tune of 0.5%. So you know looking at it all in all there's really no reason why European equity markets and particularly DAX can't actually test 11,000. That's not to say that we may not get a pullback. Certainly the breakout level that we saw earlier this month is around about the 10,100 area so we could get a dip back to there. But overall there's really nothing to stop it from going progressively higher. And I think really it's the same sort of scenario with respect to other European equity markets. We've got a significant breakout here on the Euro 50 and that consolidation breakout suggests that we could well see a much sharper move higher. Given the fact that we've not only taken out the trend line resistance from the September highs but we've also taken out the September highs as well. And if we measure this move here, this measured move here upwards that really takes us up to round about 3,600, 3,700 on the Euro stocks 50. Still way below the highs that we saw in 2007 and 2008 but nonetheless still a fair bit higher overall. And I think it's going to be a similar sort of story for Italian markets and Spanish markets as well. We've broken above the 200 day moving average in the Italian market. And while we hold above the 200 day moving average technically there's no reason why we shouldn't start to push on towards the September highs that we saw above 21,000. Simply because investors seem to think rightly or wrongly that all this extra cash has to go somewhere. The likelihood is it's going to go into equity markets. It's probably not going to make that much difference in terms of the economic growth picture in Europe. But certainly the continued decline in oil prices is probably going to help in that regard. Now oil prices are slightly higher today but at the moment they're largely trading in a range and I'll look at them in a minute after we've looked at the UK 100. Because the UK 100 is starting to look particularly interesting in terms of where we could go over the course of the next few days. We're once again approaching these range highs that I've talked about at great length over the course of the last few months. And we can see here in through the May highs, September highs, there's a big, big resistance around the 6,900 area. So it's certainly worth keeping an eye on those series of peaks around about 6,900. The all-time high just as a reminder is 6,950 and that really I think is the key, key level for a test on the 7,000 level. At the moment there's no reason to suppose we won't continue to trade in the range that we've been trading in for the past few months. But we certainly need to keep an eye on those peaks for any potential breakout move higher. So let's move on to currencies. It's been pretty much a one-way bet with Eurodollar over the course of the last few months. We're certainly, we're down 17% Eurodollar from the levels that we saw in June of July last year. And it's been akin to trying to catch a falling knife with respect to Eurodollar. But I think there is at some point there's going to be, there's going to be an occasion where we could well get caught out with a short squeeze. Now at the moment we do appear to be finding some buyers around about, around about the 111 area, 1.1.1. 1,1205, let's have a quick look at that because that's significant in the context of the overall move that we've seen higher in Eurodollar from the lows that we saw in 2000 at 82.30, not .8203, to the highs that we saw in 2008 at 160.20. That level is 1,1206. It's a 61.8 for an actually retracement level of the entire up move from those all-time lows to those all-time highs. So certainly 1,1205, 1,1206, what I'd like to see on that is a monthly close below 1,1205 to suggest that we're going to see a further move lower. Let's also look and zoom in on this chart as well. We've had 1,2,3,4,5,6,7 successive monthly declines in Eurodollar. Can we make it an eighth? I think it's a big ask in terms of where we go next. And I think there's also a presumption that the US is likely to raise rates sometime this year. Now I say a presumption because I think it could well be a mistaken presumption. I certainly don't think that when you're looking at the various inflation scenarios that are playing out in China and the inflation scenarios that are playing out in Europe and the UK that that inflation scenario won't also start to factor in to this week's FOMC rate decision, which is due on Wednesday evening at 7pm. The fact is markets are pricing in a US rate hike this year. I still maintain that that is probably, I think that's probably 50-50. I certainly don't think that it's likely. I'm still in the minority when it comes to that. But I certainly think as more and more US economic data comes out and the more it becomes apparent that the US Fed is going to start missing its inflation targets that we could well get a bit of a sell-off in the US dollar. And as a result, you could actually see a significant short squeeze and a lot of the dollar denominated currencies like euro dollar and the pound against the dollar. So it's certainly worth keeping an eye on this 1205 level, 112 level. I think for me what we need to see is a weekly or a monthly close below this to suggest that we're going to get a move to 105. We're certainly seeing some massive divergence on the daily charts with respect to that and certainly what I would hope to see is a move back through 113.5, back through 115. Let's draw a trend line on this so we can get some sort of indication as to where the levels could be. There we go. Keep an eye on that trend line there. It could give us a sharp indication of a significant short squeeze if we break above it. Certainly you can see it much better on the four-hour chart. Keep an eye on it. I certainly think there is some evidence that maybe the market is getting a little bit short. Looking at the client sentiment, we can pretty much tell our top clients are 96% short, which is 5% up from the same period on Friday, which does seem to suggest that the market is starting to get short just below 113, which is where we currently are at the moment, around about 112. So certainly keep an eye for a potential short squeeze there. The four-hour chart is starting to look as if it's about to tick higher. Maybe we could get a move higher there. Similar sort of story, I think, on the pound against the dollar as well. Keep an eye on the 150 level. We've tried to push below it. We haven't as yet been able to actually sustain a move below it. I think from a psychological level, it's a pretty important level. If we have traded below it, I think it's triggered a few stops. But overall, again, we've been in an overall downtrend for quite some time, but I certainly think there's potential for us to go for a little bit of a trip back towards the upside. First resistance level is really around last week's highs, around about 151.40. But we've also got pretty solid support between 148.10 and 148.30, and that was the double lows that we saw in 2013. And we can see that here. 2013, we found a couple of areas of significant support through there. So I think that's really a key level to keep an eye out for going forward. I certainly think that there's more risk of a short squeeze than there is for further losses at this point in time. But again, as with anything, it's about playing the percentages. Certainly looking at Euro-sterling, again, it's pretty much been a strong move lower over the course of the last few days. But again, we're seeing significant evidence that potentially there is certainly some interest to buy around about 74. So certainly worth keeping an eye on that. But we could certainly squeeze all the way back quite substantially to this trend line here from the highs that we saw at the end of last year. And we can see that the December high is there. We can probably go all the way back to around about 76, 75, 80. That's the last area of support before we broke lower. We've been down two cents since then, and that does suggest that maybe we could get a rather violent snapback if we got any data to warrant it. And certainly we're back around 75. So, again, worth keeping an eye on Euro-sterling. Let's look at Dolly Yen. Dolly Yen, again, we're getting a little bit of potential build up here. We're in a bit of a range. Solid support around about 115, 60. Resistance coming in around about 119, 119, 20. We're in a bit of a range. And I think at the moment that's just being a little bit sidelined by what's happening on the Euro. And the Euro crosses. But certainly worth keeping an eye on if we get towards this resistance line from the highs in December. It's certainly worth, again, having a look at if we get anywhere near the support from the lows that we saw in the middle of this month. Looking at the crosses from Euro Yen, broken down towards and through 134. And 134 was a huge level on the way down. We can see that from this weekly chart here, all the way through here. We've broken below it, but we haven't as yet been able to take out this series of lows through the end of 2013. So we've had a little bit of a look down around about the 131 level, but we haven't, again, been able to sustain and move through it. So again, it's certainly worth keeping an eye on any potential short squeezes here because of overextended short positions. Just get rid of that for the moment. Keep an eye on the chart forums for any updates. It's certainly worth keeping an eye on. Looking, again, at the client sentiment. Again, it's predominantly being played from the short side. So once again, it just goes to show that the market is very, very much one way. And it's certainly something that you do need to be aware of. The trend is your friend, but also be aware that we've had some very strong moves in the course of the past few days. And that's certainly shown by these candles here. We can see that. On Friday, we saw significantly big range, 135, 130 and one day. On Friday, we saw 137, 134 on Thursday. On Thursday, we've seen 133.5, 130. So Euro yen is moving in between three and five big figures in one day, which makes it very, very expensive if you're the wrong side of it. So let's have a quick look at gold. We've had a bit of a set off in gold despite the fact that the ECB has launched a large-scale quantitative easing program. And at the moment, it's not hard to see why. You can actually see the breakout here with the inverse head and shoulders reversal. Now the initial target for that move is around about 1,340. We've hit the 61.8 level and we've started to run into a little bit of selling pressure just above 1,300. As long as we stay above 1,275, then the uptrend remains intact. And even if we do drop below it, we're still above the 200-day moving average. So we could get a drift back to around about 1,275 or even as low as around about the mid-1250s. But overall, as long as we stay above those two key levels, then the breakout that we saw earlier this month, it appears likely to build on that and push higher. But we do need to bear in mind that we do have this trend line resistance coming in just above 1,300 from these peaks here in the middle of 2013. So certainly there is an area of natural resistance just above 1,300. Maybe we need to work out some of this overbought nature of this market to, again, once again, re-establish and then go higher and test the long-term minimum price objective around about 1,340. Moving quickly on to Brent Crude. We can see from this chart here that we're pretty much stuck in a bit of a range at the moment. It does appear to be fairly well supported around $47 a barrel. We can see that on this two-hour chart here over the past couple of weeks. We've traded pretty much between support $47. It's found quite a few sellers anywhere near or around $50, and that does appear to be the way of it at the moment. Certainly in the context of the Saudi supply story, nothing has changed with the death of the Saudi king. The policy is likely to remain pretty much the same. There's more supply than there is demand. Saudi is likely to still keep its foot in with respect to pumping out as much oil as it can to maintain its market share. It's already seeing some of the results, some positive results from its current policy. We've already heard Halliburton and Baker Hughes, both oil-filled services providers, announce they're cutting back on re-counts in the US, which suggests to me that the policy is starting to reap dividends, and we've already seen one US shell producer go bust in the past three or four weeks, WBH Energy. So I would suggest it's unlikely that the Saudis would suddenly change their policy when there's clear evidence that it's actually starting to work. We'll finish off with the Australian dollar because we've got Australian inflation data later this week, and we've had a significant breakout lower than the Australian dollar over the course of the last few days. And it's quite a key resistance or support level that we've broken through. If we look at the monthly chart, we can see the overall move from 60-10 lows to the highs at 111, and 61.8 Fibonacci retracement level currently comes in at around about around about 79.50, 79.75. So that's really a key level on the monthly chart. We've got the 200-month moving average. Again, a certain degree of support around there. But given the fact that we've broken below these series of key levels here, then the momentum does suggest we could well see further Aussie losses, and I think largely predicated on the basis that the RBA could well be forced to cut rates to react to the rate cuts that we're currently seeing come through from other central banks, namely the most recent one was the Bank of Canada. So the key resistance on Aussie dollar at the moment is 79.50, and then 80.35 on the top side. In the same way, Dollar Canada, again, we look at the break high that we've seen back above 124. Again, that looks a little bit over-extended over the course of the last few days and weeks. And that does seem to suggest again that any US change in rate expectations could actually see Dollar Canada slip back quite sharply. Okay, so that's pretty much it for this week. Once again, I'm sorry about the technical problems that have caused me to actually pre-record this and not actually host it live. But if you do have any questions that you want to direct my way or my colleague Jasper's way, you can find us on Twitter. Jasper's at Jay Lawler underscore CMC. Otherwise, we'd like to thank you very much for listening and we will speak to you all next week.


I'm hanging out with the MC for today, Dr. Ofweleke. MC, MC, I'm a tangana fundraising. Pole, pole, bro. Yeah, the host of the event. Alright guys, I take it back, I'm hanging out with the host for today's cover event. How you doing, sir? Well, I'm doing fantastic. It's been a very stressful one month trying to put all this together. I was playing two roles in one. I was also among the organizers plus now also the host as well. But I'm happy for the days here. So I'm really, really happy. Oh, okay, now I know Akode is a very choosy woman, you know. She chooses the best. We all know that. What makes you fit for this particular event? Well, one is because I'm really, really good at what I do. I'm very disciplined. All at this, the cameraman is telling me to face the camera. Well, because I'm good at what I do. I'm meticulous. I'm strict. And I love my job and it's partial. And more so apart from that, I'm a perfectionist and I think that is why I'm here. Okay, perfect, perfect. Now, what are your thoughts about what Akode is doing today? Well, tonight I'm excited because tonight we are unveiling a different kind of Akode. We are unveiling a more subtle, a more calm, a more relaxed but firm kind of a brand. That's what we are unveiling tonight. Two, we are unveiling one of the things that any human being should have in a bucket list, which is an author. So we are unveiling a new addition to her profile as an author. So I'm really, really much excited about that. Also her new album, I've heard the privilege of listening to the songs and I can say we are looking forward to a different type of Akode. Oh, what's your favorite song in that EP? There's one called, I'm trying to get the name, but it's about love. It's very deep, it's very sentimental. I'm trying to remember the name, I can't remember exactly. But it shows how Akode is human and she really actually has feelings. And that's what I like. It's a very beautiful, especially for a wedding, I'll recommend for that song. Okay, so what is that one famous quote that Akode has? Or rather she has told us that you can't wait to see on that book? Well, I and I share a lot of quotes. But there's one quote that normally says, we normally joke to each other, that you don't really dying, there's something about not really dying. Dying is not a real death, but actually you not achieving your dreams and what you're really destined to be, is actually what real death is. Yes, that's really, really, really deep for me. Yes. I believe you work closely too with Akode or rather you just close, you have a close relationship. What contribution has Akode done to your life? Akode is like my ride or die. I know that whenever I need somebody to talk to, whenever I feel like they have something that bothers me, I know if there's one person I'll talk to and I will not hear the story in somebody else's mouth, is Akode. And I think even my wife knows when she sees Akode's phone, she goes to sleep because she knows that's a whole two hours of conversation. We are really close. She's that one friend who I know, I can always lean on whenever I need somebody to talk to, somebody who we can share a few things about life. Yes. All right, when I can now aside from this, Kido, go to... Yes. Let's talk about blogger Edgobare. You know, some time back, you were a guest of him and he talked to you, you responded to him, but I would like to know, what are your thoughts about what he does? I think there are more important things to talk about. Come on. That's all I can say. Edgobare is earning his living. And like I told him, you earn your living bro, but what I tell people is not even Edgobare alone. I've been very keen on telling bloggers, I don't need to explain to people about my personal life. I give you guys Drofenike, that should be your concentration. Where is my next show? What am I doing? That should be a point of focus. A point of focus should not be about my children and about my wife. I did not invite... I did not call you guys when I was wooing my wife. So I don't feel that I should also explain to you guys when issues are not okay or we are okay. And I deliberately don't post my family on social media. I don't do that because it's about me. When you go on my Instagram, it's about Drofenike and that is what I want guys to consume about. Because I feel it's really unfair. Two things that are unfair. One, it's unfair for me to expose my wife to all these social media bagajia. She didn't ask for it. Her fault was just to marry me. Her fault was not... She didn't bargain for all these social media nonsense. Number two, I feel it's unfair that we only give marriages, celebrity marriages attention when they're in issues. Why are we not celebrity marriages that are successful? Why are we being the guys to sell the narrative that marriages are not working on generation because media is a tool. And I think we're using media as a negative tool when it comes to marriage. We want to highlight when issues are wrong. And I'm sorry, if guys are waiting for me to be a statistic about my marriage, man, you all better grab a cocktail and relax because my marriage will not be a statistic. Exactly. That was quite elaborate right there now. Fuenike, what are we expecting tonight? Tonight we're expecting a beautiful launch of beautiful songs. We're expecting a launch of a book that anybody who is keen to learn is going to feel some kind of a change. And I'm excited more because we, just like I said, we are unveiling a different type of an akove. Yes, that is what I'm excited about. Yes, and also just as being the head and just making sure the whole event runs smoothly. Of course, there's a lady called Sarah and of course there's a guy called Fred and Akove's daughter is as the team behind the event, we're just happy and looking forward to see the event being successful. And so far, so good. Yes. All right, we are definitely looking forward to that. Thank you so much to SPM, you guys are doing an amazing job. Thank you. I think you guys are really not a big shout out to my brother, but you guys are well-planned, you're very organized and your content is legit and that's what we're celebrating. Shukran, thank you. I have not seen useless gossip on SPM. The day I do though, I will tell you. Please do. But so far, I'm very much impressed by SPM. All right. You guys are doing a good job. Give credit where it's due. How are you? Beautiful. Thank you. All right. All right, guys. That was Dr. Ofoenike. He is the host for tonight Akove's EP launch and the book launch. We can't wait to see what he does.


Hey guys, it's Tillie and today I'm here with another video, and if you haven't read the title already, I can tell you if I'm going to be one of my favourite videos that I'm ever going to film or upload to my YouTube channel. So today I'm basically going to let my animals pick my TBR. And a little while ago I did do videos on my YouTube channel, which was Pick My TBR, which is where you guys got to pick the books that I read for the month, and this is kind of like a version of that, except that my animals are going to pick it. And it's going to be extremely cute. So I'm kind of battling against the weather at the moment, so I'm not too sure what the audio is going to sound like. Like, of course, when I say that the wind just extremely picks up. Hopefully it's not going to be too bad, and I can work with it and if not, I'll do some voiceovers, because that'll be fun. I think what I'm going to do is I'm going to put three books in front of my animals and let them choose them, hopefully by knocking them over or touching them or something, we'll figure it out along the way. So this one here is Kel, who's like the alpha of the paddock, my little unicorn baby. The side team is Buffy, our big, big, buff-head sheep. Over here we've got Lila and Gertie. These are the friendly two. Then we have our main boss, Foxy, over here. She is the dominant of the paddock, and if she wants something, she gets it. And I don't know if you can really see that head outline down the back of that shade cloth. That's George and his stuck. Hey, buddy. He's stuck. You can back up. You're all right. They've actually chewed out a little bit, so I'm going to bring my books into the paddock and hope that I can pull this off without them eating them. These two literally just want to choose all of the books. Alrighty, let's see if this works. So it may not look like it's working, but I was still super optimistic at this point and for good reason. Oh, damn. Kel chose uprooted by Naomi Novik. These two are just not feeling like behaving at all. So I'm going to give them some extra food and hopefully that'll calm them down because Lila just stood on three books and left dirty footprints all over them. This just isn't working. I can't even put them down and be quick enough to stop them from touching them.  Kel, no. Don't even think about it, Lila. Let's go back to just 43 seconds ago when I said this. Hope that I can pull this off without them eating them. Mayday, they are eating the books. I need to evacuate this area. Come on, out of here, come on. This turns from good to bad very quickly. Oh, she chose. Lila, give me the book back. This is not working out how I planned. Kel, this is George's turn. Kel, pick a book, baby. Kel, Kel, now look what you've done. This is why we don't have nice things, Kel. This is why. This is turning out to be so much harder than I anticipated. I am sweaty.  So I'm moving on to a different group of animals. I feel bad that the goats did ruin all that fun for the sheep and horses, but we're going to see how the chickens, ducks, and geese go. So far, we've got who's afraid, the dry, and history's all you left me. We're going to see how this goes. I've decided to try and bribe them with food around them, but so far to no avail. That's Jerry.  The lady at the back's the cutest, so she's blind. 11 minutes later. Fun fact, the record for multiple egg yolks and one egg is nine. What I've learned about having chickens is that they love to eat egg. It drives them crazy. The truth is showing the egg. I have two chickens now entranced. So let's see how this one goes. I'm just going to crack it on my camera. Oh my God, what if I knock it into the egg? Oh my God. So this hasn't turned out how I expected at all so far. I'm literally have just been left with like super dirty books. Ew. What are you eating, Pip? Pip, put that down. She just ate that entire one. Pip Junior spit it out. Yep, I resorted to bribery. Not only bribing my dad to help me, but also trying to get the dogs to just knock a damn book over. It wasn't working. I was really relying on Pippa to help me out on this one, but all she was interested in was just showing me some love. What's this? What is that? What is it? Okay, she picked the love that I have. You guys saw that. Her nose touched the book and that counts. The love that I have has won this round. Oh, the moment that I pretty much want to grab Terry to film this, she decides to climb up a tree. Terry, don't go further. Terry. Terry, back it up. Back it up, Terry. Terry, come pick a book. Just knock one over. Don't walk around them, Terry. So, because she doesn't really want to pick something, I've had to resort to a little bit of bribery. She's showing the gentleman's guide to vice and virtue. Special mention to Mr. Shadow Bean, or Spine, as I call him, and his mother over here, Forrest or Fofi. She's like the cute, grumpy old cat that bites. And this here is Melly. She is my seven-year-old and blind cat. So there you guys have my animals pick my TBR and I was a lot more chaotic than I expected it to be, but they did actually manage to pick a few good books for my TBR. Huge shout out to my animals for being amazing, as always. I really do love those guys, even though the goats ate some of my books. It's still fine. I love them. Thank you guys for watching, and I hope you guys have a lovely bookish day, and that great things happen to you. Telling you today I'm here with another video, and this one is going through my top three favorites and least favorite reads so far of 2018.