It’s not pretty so far. But you can log in, view a list of your feeds with current value, and see a graph of the last 24 hours of a feed.
My aim is to make it like the Android app.
If anyone wants to help out, let me know! I’m using it as a way to try out some new things, as well as try out Swift 3 properly in a brand new app. I can talk through the design philosophy with anyone who wants to chip in. I’d love to collaborate on this!
I was going to try out React Native which would have the added benefit of being easier to do an Android version. But I ended up getting a bit bogged down, and realised since my skill really lies in pure iOS, I should stick to that.
We can ensure this even without a combined code base. Even these cross platform libraries you only really get the benefit of sharing some layers of the code - and that layer would be quite thin on an app like this.
Sweet! Yeh I will set up a beta test program once I’ve got a bit further. It’s very early days so far. I’m sort of playing around with some new Swift/iOS shinyness while I’m making this.
It pains me that we have to write these 3 times - WWW, Android and iOS. And then there’s the massive duplication between MyElectric, MySolarPV, etc.
The styling needs to be done for sure, but this is basically a straight clone of the Android My Electric app. Funnily enough, the charting library I’m using is a direct port of the same charting library that’s used on the emoncms Android app. So getting things looking similar is pretty easy!
Just a few more tweaks on that and it’ll be usable. Things that need doing:
“Use today” is clearly not right - it’s just the current value of the kWh feed. Just testing!
Bar chart needs a little bit of styling to get the nice M T W T F S S in the bottom of the bars.
It needs to auto-update. And probably a refresh button in the top right.
It needs buttons to change to 1 hour, 8 hour, 1 day, zoom, pan, etc.
for what it is worth - I like the nice clean white background like in the first post. I am personally not a fan of dark backgrounds. Just my 2 cents worth as an armchair quarterback / back seat driver!
Hi Matt, Like what doing, personally I do not use iOS but I was interested by your original approach which looked more like the mainstream or full emoncms feed page than the emoncms apps. Is that a route you intend to pursue further or are you now going for the emoncms apps as the main feature set?
With regard to the MyElectric and MySolar duplication, I wanted to mention some change in the pipeline for the AndroidApp that I would also like to add to the emoncms web apps, so you may want to concider them here too?
Whilst the MySolar app is quite specific to the overall picture (but could have alternatives eg your MyDiverted app or hydro/wind etc) and would usually (but not always) only be needed once in any account, the MyElectric app is a simple report based on a single power&energy feed pair, This could be used for several different feed pairs to report a multitude of different things from the more obvious electricals (eg EV charging or hot-tub heating etc) but also as “rate & total” pairs, other instances of “MyElectric” could also report gas, oil or water consumption or even rainfall etc too.
It would be good to collaborate and move the AndroidApp, emoncms apps and the iOS app forward together for this, if you have any interest in making “myElectric” a group of user defined (freetext title/2x feeds/1x colour each) pages rather than a single page, I think many users would find this extremely useful.
I tend to agree. I just wanted to make it the same for now. Although it doesn’t really fit in with the iOS way. So I think it does need to change.
Totally agree. I would love to add something like that eventually!
YES YES, and YES. Any thoughts on best ways we can collaborate? Should we have some place where we discuss things? And maybe come up with a combined roadmap? This goes with your other points. It would be great to share a roadmap so that we can keep track of where everything is going so as not to diverge, and also share in the thoughts of each app.
It’s part of my design from the start for iOS. It’s not there just yet, because it’s not top priority, but it’ll work eventually
I actually like having an open discussion in an easily accessible and central location, like here on the forum and then raising specific tasks/bugs/todo’s etc as issues on GitHub, that keeps the chit chat out of the “issues” and keeps everyone involved in the discussions rather than developing behind closed doors, from the forum, issues can be linked rather than spreading one discussion across many locations. In this instance though there are at least 3 repo’s (iOS, Android and web apps) in play and with multiple contributors this could easily double/triple.
Since we will not all get access to multiple emoncms repo’s to make use of the issue tracking labels, assignment and milestones I could set up a dummy/temporary github repo just for some central issue tracking during development, that way we can all have some access.
Yeh, having the discussion on here is fine. I just wondered if we should ask for a separate section? Or actually, we can just use a tag. I tagged this post with “mobile” for example. I’ve not used Discourse much, but maybe there’s a way to subscribe to a tag so that interested people can be notified when there’s a mobile discussion going on?!