Adding data points.
Saturday 13 February 2010, 4:05AM - Comments
You can now add data points from the Data Points view (reworked the design a bit too):
On features: don’t make false promises.
Saturday 13 February 2010, 3:51AM - Comments
Never. It doesn’t matter if it’s some small little thing, people will probably be mad (even though they haven’t even used or paid for the app yet) regardless. Even worse: removing features. Make sure you want a feature before you tell anyone about it.
And that’s the foreword to: you can’t move data logs into folders. You can still edit the name/icon/unit, but you won’t be able to move data logs in and out of folders. In the first release. It will be coming in an update (updates will be frequent, if you use my other app Twizzle, you’ll know 
). There are just too many bugs to solve before this happens.
After the first release, I’m going to convert the entire data-saving mechanism to Core Data, which will make this way easier. And then you’ll be able to move data logs into folders.
So sorry about that. Hopefully you guys won’t beat me up over the head with a stick. If you’re sincerely mad, just email me and I may be able to give you a promo code to make up for this blunder.
To cheer you up: a new feature I just added is clearing a data log of all it’s data points. 
One more day, guys!
Choices, choices, choices.
Friday 12 February 2010, 2:05PM - Comments
It may very well be that my first 10-minute job gets the role as Dayta’s icon. Which of the three is your favorite? What improvements could I make to make it… better?
Make your voice heard!
Data Options.
Friday 12 February 2010, 10:06AM - Comments
The only page I have left to do, before Dayta is basically complete (feature-wise) is the Data Options page. I think I should be done today, minus bugs. Tomorrow’s bugs and polishing day. Sunday’s submitting day (hopefully!).
Here’s an image of it (a tableView with a bunch of preferences will go in the black space):
Use Core Data. Please.
Friday 12 February 2010, 10:02AM - Comments
This is just to tell everyone: YOU SHOULD USE CORE DATA. The way I handle data is basically by managing a plist-like object, kind of like an array. The problem with this is – while really fast to get off the ground, which I needed to finish this app in a week – that managing context is hard. Really hard.
For example, I have to record every page that the user visits, to make sure to save/edit/delete the correct pieces of data. Until now, it was pretty easy to deal with. But I’ve hit a huge challenge: the ability to move data logs into and out of folders.
Now I have to track the movement of a log to and from folders, without the aid of view controllers being pushed and popped. I’ve got most of the bugs sorted out, but there are still many more I have to deal with.
That’s why I haven’t posted once today: I’ve been working on this stuff.
Core Data manages your context for you. Use it.
Dayta’s icon – an attempt.
Thursday 11 February 2010, 3:10PM - Comments
Taking a break from code before tomorrow morning/afternoon (when I implement all of the data options stuff), I had a shot at a concept for Dayta’s icon.
Yes, I know it’s not that great. It only took me around ten minutes pulling assets from various places. But it’s a good segway to what this blogpost is really about:
What do you think would make a good icon for Dayta? It could be almost anything, as Dayta is so versatile. And of course, I love having opinions to look at besides my own.
Go!
Forethought: how much?
Thursday 11 February 2010, 12:55PM - Comments
Some have asked, and one person using a especially long comment, how much thought went into Dayta before the week started.
When I concieved the idea of One Week App a while ago, I thought about what app I should settle on. But I didn’t think much about it. I had always wanted an app that I could track certain things in my life with, but that was it for that “idea.”
So how much forethought? Basically, none. I wasn’t even sure I was going to pursue Dayta until halfway through Sunday.
And the first day that OWA began, I didn’t even start coding Dayta because I was busy doing up this here blog. That’s how much work I did ahead of time.
So you could really call this One Week App And Website (And A Ton Of Other Stuff, For Example I Had To Design An Email), and still be pretty darn accurate.
Meet me halfway (through the week).
Thursday 11 February 2010, 10:23AM - Comments
Fortunately, I won’t make you listen to that song. Anyways, I’m halfway through the week. I’ve got folder management down, data input down, the basic graph down, and more. I still need to do data options (never had time before this video, sorry), exporting of data, implementation of goals (THIS IS A MAYBE), and a bunch of little bits (like the icon).
Anywho, here’s the video you’ve been waiting for. You have been waiting, right?
Vimeo video:
Dayta – halfway done. from Sahil Lavingia on Vimeo.
Youtube video:
Onwards I go! I can see the light sleep at the end of this tunnel.
Data options.
Thursday 11 February 2010, 8:02AM - Comments
So, I’m currently working on the options that are present for each data log. This is the last feature I work on before I make the halfway video. :O
My question to you: what options do you want?
Currently I have:
- Move log to a folder.
- Change name/icon/unit.
- Reset data point every day/month/etc.
- Consolidate data values automatically (merge all of today’s into one value, either by taking average or total).
What else do you guys want?
The PSD that rules them all.
Thursday 11 February 2010, 7:43AM - Comments
For me at least. This is the PSD I use to begin every project. It has an iPhone frame and a background layer, which hovers over the rest of the design. It makes it super easy to design within. Check it out at http://oneweekapp.com/psds/. And no, I have no idea what this might be doing to my server.
