Update 1.1.2

New maintainence release with the following:

Fixes:

  • Fixed several crashes that were occurring in iOS 10. Looks like Apple changed how categories work and a prior technique I was using to prevent crashes was now actually causing them.
  • Fixed them issues. Some themes were not being displayed properly or lost colors, espeically in the Navigation bar.

New:

  • I added 12.9 iPad Pro support. Please be aware that any existing custom views you created on the iPad Pro will no longer be there. Sorry, but you'll have to recreate them. This is because, technically, the prior version of Flexile was operating under the old iPad Size (non 12.9). I looked into way to try transferring old layouts to the new version but non worked. My apologies for that.

Entering Maintenance Mode

A couple days ago I released another version of Flexile that included quite a few new features. I also made Flexile free. I know it's been quite a while since I released an update so I want to explain why and what you can expect of Flexile in the future:

Flexile has been a great experience for me but, as many of you know, it never did make any money to speak of. Over three years the app has made less than $3k in total revenue. To be honest, this was fine. I was ok with that. Flexile was (and still is) my own app. It's the app I want for myself and eventually, I think it can be a money maker. But I have a lot more developing to do before that can happen.

In the meantime, I somehow managed to spawn a child with my wife (huh...funny that) and financial pressure forced to me to divert my attention away from Flexile to other pursuits that yield a bit more than $1k a year. So I started contracting as a freelancer. This has been great, but unfortunately I haven't had the time to devote to Flexile that I should.

This latest update was a culmination of work mostly done before I had started freelancing. But because of time constraints, I wasn't able to test is thoroughly before release. So I expect there will be quite a few bugs in it. However, I've already started compiling a list of the bugs and will be releasing bug fixes in the near future.

For the short term, I will continue to release bug fixes and platform updates for Flexile. I will probably not be releasing any new features for a little while. My goal will be to keep Flexile stable and bug free. Eventually, I will continue to add to Flexile. As I've mentioned before, this is an app that I use so I won't be giving up on it. But most of my attention will be elsewhere.

I just want everyone to know that Flexile is not abandoned. It will continue to grow more stable and bug free as I release maintenance updates. But I won't be adding anything new to it for a little while. This is probably best. Flexile was one of my first apps and as such, I've learned a lot since I first started developing it. Eventually, I'd like to rewrite it.

iOS 7 & Update 1.0.8

Yesterday I submitted to Apple, Flexile Update 1.0.8.  This is a major update that includes changes to Flexile's themes and user interface as well as the addition of several new field types and features.  For more info, see the release-notes.  To be honest, I had hoped to submit this before  iOS 7 was released, but like almost every time-goal I have ever set for Flexile, I missed it.  I always seem to underestimate exactly how much work goes into features I want to add. Although as far as "misses" go, this one is fairly minor... only a few days.  

Unfortunately, I discovered early Saturday morning that the current release of Flexile (1.0.7) was crashing on iOS 7 and rendering it almost useless.  For those that are experiencing this: I am sooo sorry.  When iOS 7 was released to developers I was already well underway with the new update.  I started using it on iOS 7 and while there were certainly bugs, this crashing bug wasn't there.  I should have tested 1.0.7 on iOS 7 but I was planning on releasing the update before iOS 7 dropped and I was too busy working on the update... lesson learned (hopefully).  Version 1.0.8 is a big update, but I plan on releasing more incremental updates in the future.  This is almost required now that iOS 7 auto-updates apps.  

The next week or so I'll update the website.  Not only does almost every image need to be replaced, but I've also got some neat features planned for the website itself.  And, of course, I've got more support I need to add for the new features in Flexile.  All of it "Coming Soon".  Until then, most of the content of the website is still valid, if not slightly dated. 

Crash Reporting

So, funny thing happened.... bugs.  This last build included an integrated "crash reporting" service, Crashlytics, that compiles and emails me whenever Flexile crashes.  While I do a lot of testing, and my beta testers fill in the "gaps"... there's only so much a dozen people can actually cover in an app as large and as complex as Flexile.  Knowing when a crash occurred would help me a lot.  So this past update (v 1.0.6) was the first update to include this reporting service in a public release of Flexile.  Now, I had been testing/using this service with my beta testers for the last couple of months and I found it incredibly useful.  However, I didn't really know what to expect when it was released into the public.  On the one hand, I kind of hoped that not much would happen, as it would mean Flexile was pretty much bug free.... not that I really expected this.  On the other hand, getting thousands of crash reports would mean I should really reconsider my chosen profession.

Luckily, I didn't get thousands of crash reports.  I did, however, get a few.  Enough of them that I decided to squash them quickly and put out another update.  It's very important that Flexile is stable, which is why I'm using the Crash Reporting service in the first place.  I especially found a very "pernicious" bug in the new Sidebar that occurred if you added, deleted or moved a Table Section.  It's kind an obvious bug, except that me and (I suspect) all my beta testers have already 'fleshed' out our databases so we don't actually mess with that part of the app very much.... <sigh>... a bad oversight.  I've already implemented the fix and submitted the update.  Assuming no more 'major' bugs come in, the update should be approved by early next week (possibly sooner if Apple is feeling efficient).   

If you want more information about the bugs that were fixed, please take a look at the Release Notes for version 1.0.7.

Privacy: I want to assure you that even though Flexile now reports to me when it crashes, no personal information is transmitted.  Essentially, I receive a report that tells me when the crash occurred, some device information (iPad, iPhone, etc) and where in my code the crash occurred.  Your data isn't transmitted.  

Import

I've finally finished the Import and Export for Flexile.  The import especially is very sophisticated, allowing for duplication detection, splitting import columns into multiple tables and auto-link generation between related records.  Moreover, it was implemented with a drag and drop interface and should make it pretty easy to import your data.  Of course, I didn't neglect export, so you're data is no longer "trapped" in Flexile.

From here I plan on updating the website, which has been neglected for far too long.  I expect to be working on that for the next week or so before I jump back into Flexile development.  I am giving thought to doing a little marketing for Flexile.  While it's not quite where I'd like it to be, it is shaping up to be a pretty solid app.  It may just be about time to start getting the word out about Flexile.

I've gotten quite a few requests for a few specific types of fields in Flexile, so I intend on working on those next.  Unlike Import & Export, which took a couple months to finish, I'm hoping to release update a bit more frequently.  This should no only squash bug quicker, but also get new features into user's hands quicker.  No solid promises, but here's what I hope to implement over the next couple months:

  • Concatenation Field... I intend on providing a drag and drop interface.  Along with that, I want to look into developing a ternary condition you can insert into the formula (if ? then : else).  If that's successful, I'll probably port it over to the calculation field.
  • Running Balance Field... I've got some ideas on how to implement this and keep the data current.  I will probably also include with this aggregate total on all number based fields via a bottom toolbar in the recordset.
  • Linked Field... Currently, you can "pull" information from links through aggregate fields, but that's limited to number-based fields.  Instead, the Linked Field will pull a single value from a linked record's field based on certain criteria: First Linked, Last Linked, some <value> equal to <value>, etc.