I am with Os 2 b2 and iOS 9 b2. Please send me invitation for beta testing your appI am starting work toward 2.0 for iOS 9.
Anyone interested in beta testing? iOS 8 devices are acceptable!![]()
I am with Os 2 b2 and iOS 9 b2. Please send me invitation for beta testing your appI am starting work toward 2.0 for iOS 9.
Anyone interested in beta testing? iOS 8 devices are acceptable!![]()
Can you email me? daniel@departureboard.coI am with Os 2 b2 and iOS 9 b2. Please send me invitation for beta testing your app![]()
This looks like a fantastic app. If/when I get my watch I will almost certainly be grabbing this app.
My question is - does this handle connections (I am guessing not at the moment?)
So for example if I set a favourite destination as Norwich and I am travelling from Caterham, I have to go first into London Liverpool Street.
Something for version 2 perhaps? The ability for me to force-touch to select a destination that requires connections, then have Departure Board tell me when the next train is to the first connection, then once I'm at that station it remembers where I want to go and tells me the next trains to the second connection, and so on. I say this carefully because I appreciate that this is starting to stray into a journey-planner which I know is not what this app is for, Citymapper etc handles journeys with all modes of transport like that. The key thing is that Departure Board should remember where I want to go and update automatically the next favourite destination in the chain, if that makes sense? So it's not planning my entire journey, but keeping the primary focus: Quick information of upcoming departures.
(I have to say, the ability to set a favourite destination is one of the killer features of this app regardless of its ability to handle connections - a really good idea that you implemented it!)
That sounds good, what you described!Thanks for the kind words.
If you were travelling from station A to station C via station B. I'd suggest you create two favourites:
and enable automatic favourite loading. When near A you will see the trains to B and when near B you will see the trains to C on the phone. I am working on the watchOS 2 native app at the moment and it will also have this functionality.
- Station A - Calling as Station B
- Station B - Calling as Station C
As far as a multipart journey is concerned, I do not currently have plans to support this.
Hey there!
One thing which would make it a lot better for me on the Apple Watch would be the addition of "Via" information. If
View attachment 572391View attachment 572392
Well as I understand it - by mirroring the iOS app it would still display a favourite station first if I was close to it but actually closer to another station right?I am making the new version for watchOS 2.
When you open the app should it load to the list of local station as it does now, or should it mirror the iOS app and load a departure board?
Still looking for more beta testers.
Version 2 has been submitted for review:
Features:
- Show Arrival Time
- Show Earlier Trains.
- Handoff Support (transfer sessions between iOS devices and from Apple Watch).
- Spotlight Indexing of all stations and favourites.
- New Apple Watch App with watchOS 2 Support.
- New Apple Watch Glance.
- New iOS Today Widget - access your departure boards from anywhere in iOS.
- URL Scheme Support - launch the application directly to a specific train station with optional calling point filter.
Tweaks
- Split View Support (side by side: station list and train service list on wide screens)
- Moved Favourites from separate tab to top of list if any are set.
- Moved Favourite icon.
- Made all Navigation Controller Transparent.
- Changed title of refresh controller when changing station from CRS to station name.
- MANY tweaks and bug fixes.
It would be nice if it showed anything at all! Since WatchOS 2 Departure has been extremely buggy on my AW. It worked perfectly before the upgrade.I am making the new version for watchOS 2.
When you open the app should it load to the list of local station as it does now, or should it mirror the iOS app and load a departure board?
It would be nice if it showed anything at all! Since WatchOS 2 Departure has been extremely buggy on my AW. It worked perfectly before the upgrade.
I had already sent you an email with all the details but didn't seem to have had a reply. Just found your reply in my spam filter and have responded. Sorry for the confusion.What isn't working? Can you be more detailed? I have found a bug in the glance, but the watch app should be ok.
Can you email me: daniel@departureboard.co?
Hey,Well, I am getting this since OS2
Hi, the first step worked (so without installing the app) however the Glance is broken and does not go past the 'Locating...'Hey,
This is an issue with location access permission in watchOS 2, when transitioning from watchOS 1 to watchOS 2. To fix it:
Disable location settings for Departure Board on iOS (Settings > Privacy > Location Services > Departure > Never), then re-enable location access (Always),
If that doesn’t work.
Remove the watch app, disable location settings for Departure Board on iOS (Settings > Privacy > Location Services > Departure > Never), then re-enable location access (Always), then re-install the watch app.
Apologies for the inconvience. Can you let me know if this fixes it?
daniel@departureboard.co
I'm the same, I loaded glances it gave a little chime like when watch app loads then stays on locating...I am having problems with Glances. Just says Locating. The app works fine except under Glances. I have tried all of the above