littlelogs

Keep a social journal of your work progress as you make and learn things.

Tagged #android

March 2017

josh

More #exist #android #customtracking fun today. Trying to design an alternative 8-day graph for the Today tab that’s a bit more compact and attractive than reusing the current graphs, as they’d all just say 1 or 0 anyway. So far I have some little ticks in pill shapes that look nice. I wish I could come up with something as readable that is more compact, but all the variations I’ve tried were harder to parse. Oh well, design’s all about compromises, right?

I guess I’ll leave it at what I have for now, and muse on it a bit while I work on the editing interface.

josh

Started setting up the interface in the #exist #android app for rendering #customtracking tags. There’s probably a lot of iterating to go on making it all look just right, but I think the first 80% is done. Next step will be to think about how the interface for tracking stuff (literally, typing in your tags) will work. We also want to make it easy to add and edit stuff, but don’t want to make people think they have to use it by making it too obvious with extra buttons everywhere and so on. So yeah, even more iterating to get it just right.

josh

Woo! Got #customtracking working in a hacky way in #exist #android. Solved some minor issues with that on the server side, and then verified all works as it should. The next step will be to actually make a nice UI for adding and tracking various custom habits and events, and at some point I’ll deploy the backend stuff to the live server so we can test it for real with some beta testers.

I also spent some time helping @belle figure out more #ios #healthkit sleep logic. Getting closer!

January 2017

josh

Overnight #exist got a mention on Gizmodo! Some kind of niche section called Field Guide. Well if we thought the Back to Work podcast helped, this has been nuts — over a hundred signups today, probably our biggest day since launch. I actually thought we were being targeted by spammers initially because of all the Hotmail signups 😆 if most of these people convert we’ll be doing so much better. I’m trying not to get too optimistic though.

In more practical news I helped @belle debug a tricky Apple Health issue and released a minor update to my own #Android app.

josh

I pretty much have the new data tab in #exist #android complete, but I want to add some interactivity and hide some stuff by default so you can drill down into it.

Today I did some overdue #support tickets instead though, and later tonight I set up macOS in a vm on my pc so I can build some #ios apps. I do have a macbook, but I’d rather be at my pc. I actually got that running with few issues, and I can build apps in xcode without it taking too long — performance seems decent. I’m going to have a go at learning #swift to build the #larder iOS app. I don’t really want to steal it from @belle, but she has enough on her plate already.

josh

This week l pretty much implemented #exist’s new location name attribute, based on Google’s reverse geocoding, plus some correlations for this. I’m holding off on deploying it for now, because we decided my focus for the next few months should be adding more to the #android app. I’ve added a new tab with some trend graphs in a rather hacky manner, and just need to keep working on these graphs, correlations, and a mood breakdown.

December 2016

josh

Got #exist’s “location name” attribute sorted on the dev server today, did some #support requests, and later released #larder for #android v1.0! Nice to have the stable version out there. Anecdotally it seems like most paying users are using the app, meaning maybe it seems more valuable to Android users right now, meaning we should get the iOS app out too so we can convert some more folks. Onwards and upwards.

November 2016

josh

Today I released the #exist for #android update including the new graphs. Woo! I hope people appreciate it.

After that it was more annoying work — some fiddly support tickets from last week, and a bunch of delinquent accounts to delete. We also got some annoying “advice” from a user. The downside of being open about our troubles (in this case, on the podcast) is that people will think it’s an invitation for them to tell you at length what you should do instead. So anyway, the afternoon wasn’t a super fun time. @belle and I had another chat about Exist in the evening, as we seem to do fairly regularly, to see if we can find a new direction that we both think is good. I think part of our problem these days is that neither of us thinks it’s very good any more, and it’s hard to sell something without any conviction 😐

Ups and downs I guess.

josh

Today’s work got somewhat sidetracked by brunch with @belle, her dad and his partner — but also my car wouldn’t start, so after we got home from that (having had to walk, the indignity of it!) I waited around for the nice roadside assistance man to come check and replace my battery. All sorted now.

Later on I fixed some styling issues with the new #exist #android bits on older OS versions, and added imperial support to the graphs that I totally forgot. Pretty sure that’s everything now. Will probably release it early next week.

josh

I think my work on #exist for #android is done, barring any bugs. I’ll keep testing it for the next few days, and also make sure that it works on some older android versions. You can see a screenshot here. I’m pleased with my progress! Although I don’t know if I write android apps “the right way”, I can get things working pretty quickly these days (with liberal use of stackoverflow). I finally understand how all the pieces go together.

I’m thinking some marketing efforts next. @belle has kicked off some #changemap #customerdevelopment which means hopefully soon we’ll know what other potential customers want from it — but until then, I’ll be doing Exist and Larder-related things.

josh

Today I did some #support, then worked on the #exist #android app. I ended up forking the chart library I was using and fixing the alignment issue I had, which was thankfully pretty simple. I have the labels rendering the correct values now too, so I’m nearly done with the graphs. Next I’ll get the in-app activity feed sorted, then it’ll be deploy time.

josh

Today I worked on adding more to the #exist #android app. I’ve got the 8-day graphs in there, looking similar to the web version and sliding open and closed just the same, but I’m not 100% convinced by this graph library. I’m not sure if I’ll fork it and fix my niggles, or keep looking. At this stage it seems easier to fix it than rewrite my code to use another.

Also tonight I finished off some birthday prep for @belle’s birthday, which is today (it’s just after midnight now). I learned I’m really really bad at tying knots in balloons 😄😢 and I’m sure all the noise I made gave it away. I forgot how loud they are. Anyway, happy birthday Belle! I hope in the next year we can make you some excellent #hellocode income and end this limbo.

josh

This afternoon @belle and I did a new #hellocode podcast episode, which we haven’t done for many months. You can listen here. We check in on Exist, Changemap, and Larder, talk about continued income woes, and wonder what we’ll even do with poor old Exist.

Tonight to keep some progress happening on #exist, I worked on its #android app, updating the tab style and starting the work to add the 8-day graphs. I’ve made decent progress in a short period, so either it’ll be done soon, or I’ll keep adding some more stuff to it to match the web app.

September 2016

josh

Making progress on the #exist dashboard redesign. Today I added some new insights based on the day of the week, and tweaked a couple of others. It’s pretty much done, @belle and I are just going to test it for a week (at least) and make sure it all looks and feels useful before unleashing it. I’ve also decided on some stuff I want to add to the mobile apps so I’ll add that to the #android app soon, probably later this week.

josh

Did some further small updates to #exist’s food tracking today. Turns out all of the US (last major stronghold of the imperial system) is used to using grams instead of ounces for nutrition values (fibre, fat etc). With our single metric/imperial units toggle we were confusing all our US users by displaying values in ounces. So I rolled it back. Since we store everything internally in metric units and just convert on the rendering end where necessary, I’ve just left those attributes as metric everywhere. The iOS app is now back in review, but the #Android app has been updated to match the web and already published.

After all that was cleared up I did some work on the new dashboard design with @belle’s feedback. More progress, slightly closer to having something we think is a big improvement.

August 2016

josh

Somehow I’ve picked up a cold again. I felt very sluggish today and didn’t get much done, but improved a little in the afternoon. Tonight I got the basics of editing and deleting working for #larder #android, so it’s almost a full CRUD client now. Just noticed we got another yearly subscription too, which is fantastic. I really think at this stage what Larder needs to grow is more people seeing it, rather than more features. Hopefully some interesting interviews on the blog will help that.

#exist-wise I am tossing up between trying to do some stuff for the weekly email this week (like including some graphs), and getting stuck into the architectural changes for #manualtracking. I think probably the email could benefit from some more useful trend info, but I don’t have a clear idea of what exactly so there’s a chance I could waste days trying various things and have nothing to show for it at the end.

Anyway, hopefully I feel a bit better tomorrow so I can get something done, regardless of what I pick!

josh

Easing back into work after a weekend away. I also followed up on some #exist #support stuff, with some more to look into later. Updated #larder for #android with a fix, and tweeted it and updated the site once it went live. I’ll email all users tomorrow.

Also realised I have to submit my case against Larder’s “disputed charge” before tomorrow. Ugh. Apparently the user lost their card and just disputed all charges from around that time. Even though he wanted to pay for Larder, and has no issue with the charge, he hasn’t told his bank to cancel the dispute. So we get slugged the penalty and go through the massive hassle of making the case that we didn’t charge him fraudulently, for a chance at getting the penalty and his charge paid back. FUN. TIMES.

July 2016

josh

Did a lot more on #larder for #android today. Fixed a bunch of little issues and missing features. Tomorrow I just need to set it to automatically refresh the access tokens when they expire, and it’ll be ready for the store. Hoping to get it done before I go away for the weekend.

josh

Today I got some nutrition attributes set up in #exist and started getting data for them from Jawbone UP. Next I’ll do Fitbit, maybe others later).

Tonight I decided I’d work on the #larder #android features missing before a beta release. One big one was login/logout (I’ve been using a hardcoded token) but I pretty much got that finished.

May 2016

josh

The last few days I’ve been trialling various #python IDEs. I use Komodo at the moment, which I quite like, but I’m tiring of it telling me “error occurred, no completions found” maybe half the time I try to use the code completions. I’ve crossed Visual Studio and Eclipse off the list of other options. PyCharm is a contender, except it’s a massive CPU and disk hog, and there are some other little niggles. Not sure what I’ll ultimately choose.

In more constructive news I’ve been writing a small update to #exist for #android to show the user’s mood note from this day last year, if they have one. I’ve missed that feature from the nightly email.

josh

I can’t help myself. Redesigned the #larder homepage again yesterday. I think this is really truly the last change for a while though.

I did a little on the Larder #android app, but various things have kept me from getting much done on it — mostly #exist #support and some old #client work. @belle and I also discussed marketing for Larder, and came up with some ideas to get it better-known. I’ll try to spread my time between the Android app and marketing work over the next month or so.

Also, today one of a precious handful of paying users cancelled their subscription after just one month, which was very painful for my ego 😞 so I emailed to ask what I could be doing better to get their business again. I hope they bother to reply so I can at least use it as an opportunity to improve the product.

josh

Today I added some images to the #larder homepage, and made a change to how the search works. The website is fine as it is for a while, so I’ve started working on the #android app again. I’m hoping it won’t take too long to get it to a basic beta state that people can use.

josh

So we launched the new #larder 14-day trial two days ago, and although I got one or two rude responses to the announcement email, overall it seemed to go down okay. We’ll have to see how it goes long-term though. I hope it converts better.

Once that was done I moved onto creating the public folder feeds for users who want to publish a nice list of bookmarks. It’s pretty much done, and I will deploy tomorrow I expect. After that I think the next big feature will be the #android app, as the web app is now “good enough”.

April 2016

josh

This afternoon I worked on the #larder #android app, styling the new bookmark UI a little, and tonight while looking for something to work on I ended up redesigning the webapp’s home page. It’s a little more spiffy and a tiny bit more explicit about what Larder offers.

josh

I’m trying out intermittent fasting at the moment, and I thought it would make me irritable and unable to work but I’m actually getting a heap done to distract myself from wanting to eat. Who knew! So today I got the #larder #chrome extension working in #firefox via its beta support for what it calls “WebExtensions”, based on the Chrome standard. There are a few bugs to iron out for them but hopefully in the next release I’ll be able to publish the same Chrome extension as a Firefox extension too. I also looked at the #safari docs and that does not look like it’ll be a fun experience.

Later in the Larder #android app I got working the basic ability to add a bookmark, either directly or via sharing to Larder. The app is now nominally read and write!

josh

Made some updates to the #larder home page today, adding our faces and changing the copy a bit. Also worked on the #android app and sharing urls to it from other apps.

Only a few people have signed up since we launched, but since it’s a soft launch I’m not too fussed. We still need to get the word out.

Then this evening I had an annoying scramble to try and fix #exist, which was timing out on all requests right as I was trying to have dinner. (Startup life.) Turns out it was just a network issue with our host and all my investigating was for naught. The whole thing was fixed in about an hour, but still, that’s a couple of incidents in the last few months. If this keeps up we’ll have the hassle of finding a new host.

March 2016

josh

Today I did some more on #larder for #android. I have bookmarks per folder downloading, caching, and being displayed in a list. And when you tap them, they open in the browser! I’d like to thank Android for making it so easy to get to this point already.

josh

More progress on the #larder #android app. I have a navigation drawer all set up with a folder list, including coloured dots, correct nesting, and bookmark counts. I’ve also been using #realm to create and query my models and I must say, it’s pretty nifty. Should make it very simple to persist the contents of folders offline and update them as needed, rather than my past approach of caching little and hitting the server every time.

larder drawer screenshot

josh

Set up some more of the #larder #API today, including the all-important ability to create a new bookmark. Made myself some OAuth2 credentials and started the scaffolding of a new #android app! Think I’ll use the “navigation drawer” pattern to hold the list of folders, which makes the most sense to me for this app’s structure, but is new to me (I prefer tabs). Reagardless, with a hardcoded access token in place, I managed to get a list of folders displaying, so I think that’ll do for tonight.

January 2016

josh

One thing I think it’s cool to note when looking back at my logs on #elm, #mithril, or even #android, is that regardless of whether you’re new to coding or have been doing it for years — we all struggle. Especially when picking up something new. Everyone misunderstands things, and hits brick walls, and makes mistakes, and writes really terrible code. My logs on #elm could be written by an absolute beginner, or I could run into the same issues as @kateo learning #angular. I think it’s a very equalising experience. So if you’re a beginner, don’t fret! Keep at it! We’re all in the same boat :)

December 2015

josh

Spent some frustrating hours trying to fix an html parsing issue in #littlelogs for #android — paragraph tags in list items break the parsing, so the app just crashes repeatedly right now. Found the issue but cannot get my head around the code for parsing text spans, so I’m giving up for today. Onward to more fun things.

josh

Finished the full preview/post flow in #littlelogs for #android tonight. You now get a nice modal dialog with a log preview, and you can edit or post. It looks pretty good! Almost ready to send beta testers a new build. (And if anyone else wants to try it, let me know.)

josh

And tonight in #littlelogs #android I worked out how to parse images out of log content (with regexes — I know, I know) and add them into the log layout as ImageViews instead. Then I pushed an update to beta testers so they can see images too.

josh

Just submitted #littlelogs for #android to the Play Store’s beta testing channel, woo! 😄 I want to stress that it’s still very early, but for browsing littlelogs on your phone, I think you’ll find it good enough. Plus I’m working on it all the time to bring it to feature parity.

So, who’s keen to test it? Comment here and I’ll email you an opt-in link! Android 5.0+ required.

Older