#Task 1
In your groups decide upon your app idea!
#Task 2
Write down what your app will do exactly. Then come up with at least 3 pictures that you will need inside your app!
#Task 3
#Task 1
In your groups decide upon your app idea!
#Task 2
Write down what your app will do exactly. Then come up with at least 3 pictures that you will need inside your app!
#Task 3
#this equals that api
These are all suggestions - I'm not an API designer - I've just consumed good and bad API's in my time.
Things I consider a good API - USGS - http://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/all_hour.geojson
A bad api example - flickr - they have numbers as strings and a stupid "root" object.
#Project Tigr Books
Getting more young people interested in technology is vital for the sustainability of the tech industry in Bath and Bristol. We've written here before about what we're doing teaching in the Bath area, and why other people should start helping us too.
We're now on kickstarter with a project to turn some of our online materials into physical books to make it easier for more people to teach their own friends and family to code. Our materials are not a railroad of instructions, unlike most typical code websites where everyone makes exactly the same thing; however they inspire creativity and everyone makes something different. For example, one book will teach creating your own interactive emoji. Our materials are also accessible
The Young Rewired State run an event each year called the festival of code - where kids under 18 get to build anything they want (but must contain some open data) and showcase it at the end of the week with all the other centers. This year the weekend was hosted in Birmingham and we had three teams presenting.
This is a run down of the things that they made!
Max made a node.js program that connected with the Bath pollution data and displayed two different sensor locations and the average pollution for Bath using littlebits. Littlebits are like lego for programming. One of the bits that I have are cloudbits - whereby we can program them over the Internet. The first picture below is some of the components that we put in a box for display purposes. This could then be used in schools or public locations to display how polluted our cities r
So the Bath Royal Literary and Scientific Institution have three trials around Bath for this summer - they'd really like it turned into an app and the tourist center have said they'd already publicise about it 😄
The three trials are:
#littleBits hack day
##1. Tools to install!
#Making Use of Glances in Apple Watch Apps
Finally in our Apple Watch App explorations, one of the features we really wanted to try out was glances. These allow people a "quick look" at some important information. In Whiskr we wanted people to be able to see the picture they last looked at quickly again. Maybe to help people check if a cat in front of them matches the one they saw on their screen.
To get started with glances, we need to save the last image viewed. We will need to use the information from this blog on how to save data between iPhone and Apple Watch app using User Preferences.
#Sharing Data between iPhone and Apple Watch apps
So we've already taken a look at some of the issues we've faced building our Whiskr Apple Watch app, next we're going to look into how we shared data between the iPhone and Apple Watch app. This was probably one of the hardest aspects to learn and get right, and the current documentation isn't all that great!
To do this we'll have to create an App Group which is essentially a space which both apps can use. It was brought in with the exetension framework in iOS8 so apps can communicate with their Today widgets, or custom keyboards, and amongst other applications.
The first thing we have to do is add the app group capability to both our iPhone and Watch Watch Extension targets.
So we're working on creating Android Material Awesome, a library which will hopefully incorperate the benefits of Material Design, Twitter's Bootstrap, and FontAwesome. What we really wanted is a project other people can easily include into their projects using gradle dependencies. To do this we needed to create a standalone library project so we could make it as lightweight as possible for including as a dependency, and a sample app that would use it for testing. These are the steps we took to get started in Android Studio (version 1.1).
The first thing we needed to do was to create two new projects, with all the default settings (Blank Activity etc). One for our sample app, and one for our library. We added both of ours into the same GitHub repo, however you can save them wherever you like.