May 2010
Summary of apps under development
May/13/2010 11:14 AM
Just a quick note regarding my works in progress:
Grasshopper: Roughly 30% code complete, I expect to ship this app Q4/2010. This app will be submitted to the Ovi Store and I have ever reason to expect it to be accepted quickly without issues. Developed using Qt 4.x, the app will initially target the N900 and N8 with the potential to support many future Qt enabled devices.
Locust: Roughly 90% of the interface and control flow have been spec'd out. Some features require device support for APIs that I have not found or fully understood quite yet; when device support for all the intended control flow is determined coding will begin. I expect to enter this app into next year's Calling All Innovators competition. This app will also be submitted to the Ovi Store and possibly other outlets related to MeeGo.
[UN-NAMED APP]: I've alluded to this app before, so here's the place holder. This app will suffer from premature feature creep for quite some time before real work is started on it. Unfortunately there is nothing I can say about this app without compromising my opportunity to be first to market with it. I expect to focus on freezing the feature set and developing the UI and control flow shortly after completing Grasshopper and Locust, though small efforts are afforded to this pet project even before completing those other two. It is too early to predict the proper distribution channels for this app.
Grub: Discussed in my last post, Grub is a project I've had several years to think about. I had dismissed it some time ago, before starting on Maemo development, due to the expected difficulties in gaining raw hardware access to the GSM radios. The idea came back to mind recently when a friend talking about Maemo development. He said, "I saw a great iPhone app [...] we should make something like that". This got me thinking on two parallel trains of thought: first that I'd rather implement original ideas; and second that it would be great if our apps utilized features of Maemo that could not be duplicated on iPhones and Android devices. Then 'bingo' this idea resurfaced. Of course Apple won't give you access to the raw hardware, and of course Android's sandboxed environment for 3rd party apps would be too constrained to do the same. I expect to work on Grub from a theoretical perspective first, followed by research into how I might gain access to the raw hardware. Grub will not possibly ship until at least late into 2011. This app is expected to be exclusively available on the Ovi store and I hope it will serve as an example of innovative potential for Nokia devices much like Gravity (the fantastic twitter app I miss so much not that I don't have a Symbian device: http://mobileways.de ).
So there you have it, 4 apps upcoming for the Maemo/MeeGo platform(s) - all from a one-man team. Grasshopper should be done this year, followed by Locust early next year. Grub and my otherwise un-named app would follow late in 2011 or sometime mid 2012. As far as project size is concerned, Grasshopper is pretty small; Locust is considerably large while my un-named app is huge. Project size for Grub will depend greatly on how much code is required to stimulate the raw GSM radio hardware and on the scope of my analysis procedures (currently not even developed mathematically, but expected to be run on the DSP which might introduce other hurdles: I've never written code to run on a DSP...). Over all I expect Grub to require about the same amount of code as Locust, but with a lot more extensive algorithms work.
I've got a few more small apps in mind, but the ideas are not yet developed enough to commit to writing them. The above apps I am fully committed to however, and you will one day be able to download and install each and every one of them. # of the 4 will certainly be made available on the Ovi Store, with Grub being exclusively available there.
Now back to work I go - I 've got a lot to do.
-bit
Grasshopper: Roughly 30% code complete, I expect to ship this app Q4/2010. This app will be submitted to the Ovi Store and I have ever reason to expect it to be accepted quickly without issues. Developed using Qt 4.x, the app will initially target the N900 and N8 with the potential to support many future Qt enabled devices.
Locust: Roughly 90% of the interface and control flow have been spec'd out. Some features require device support for APIs that I have not found or fully understood quite yet; when device support for all the intended control flow is determined coding will begin. I expect to enter this app into next year's Calling All Innovators competition. This app will also be submitted to the Ovi Store and possibly other outlets related to MeeGo.
[UN-NAMED APP]: I've alluded to this app before, so here's the place holder. This app will suffer from premature feature creep for quite some time before real work is started on it. Unfortunately there is nothing I can say about this app without compromising my opportunity to be first to market with it. I expect to focus on freezing the feature set and developing the UI and control flow shortly after completing Grasshopper and Locust, though small efforts are afforded to this pet project even before completing those other two. It is too early to predict the proper distribution channels for this app.
Grub: Discussed in my last post, Grub is a project I've had several years to think about. I had dismissed it some time ago, before starting on Maemo development, due to the expected difficulties in gaining raw hardware access to the GSM radios. The idea came back to mind recently when a friend talking about Maemo development. He said, "I saw a great iPhone app [...] we should make something like that". This got me thinking on two parallel trains of thought: first that I'd rather implement original ideas; and second that it would be great if our apps utilized features of Maemo that could not be duplicated on iPhones and Android devices. Then 'bingo' this idea resurfaced. Of course Apple won't give you access to the raw hardware, and of course Android's sandboxed environment for 3rd party apps would be too constrained to do the same. I expect to work on Grub from a theoretical perspective first, followed by research into how I might gain access to the raw hardware. Grub will not possibly ship until at least late into 2011. This app is expected to be exclusively available on the Ovi store and I hope it will serve as an example of innovative potential for Nokia devices much like Gravity (the fantastic twitter app I miss so much not that I don't have a Symbian device: http://mobileways.de ).
So there you have it, 4 apps upcoming for the Maemo/MeeGo platform(s) - all from a one-man team. Grasshopper should be done this year, followed by Locust early next year. Grub and my otherwise un-named app would follow late in 2011 or sometime mid 2012. As far as project size is concerned, Grasshopper is pretty small; Locust is considerably large while my un-named app is huge. Project size for Grub will depend greatly on how much code is required to stimulate the raw GSM radio hardware and on the scope of my analysis procedures (currently not even developed mathematically, but expected to be run on the DSP which might introduce other hurdles: I've never written code to run on a DSP...). Over all I expect Grub to require about the same amount of code as Locust, but with a lot more extensive algorithms work.
I've got a few more small apps in mind, but the ideas are not yet developed enough to commit to writing them. The above apps I am fully committed to however, and you will one day be able to download and install each and every one of them. # of the 4 will certainly be made available on the Ovi Store, with Grub being exclusively available there.
Now back to work I go - I 've got a lot to do.
-bit
New app on the list: Grub
May/13/2010 10:55 AM
So I've been toying with an idea for a few years now; I even suggested it as potential work in college for my team's senior design project (go Team Wolf @ UMass!).
I'm not announcing the app just yet, but like my other works in progress I want to be able to talk about this publicly while working on it.
Code-named 'Grub', this application will repurpose the GSM/UMTS air interface (radio) of the N900 to provide an augmented reality service that is both entertaining and useful. It's usefulness will depend greatly on factors that I can't fully predict right now; but I saved my old 'Signals and Systems' text book, as well as the text for 'Communications' so I'll dive into those for a refresher and ensure that usefulness is at least theoretically possible.
Implementing the app is another thing altogether; even if the app's usefulness would be proven so limited that no one would use it for professional reasons, the app would still be a lot of fun. So no matter what my research show, I intend to write the app. If the research shows that it cannot be truly useful then I'll put less effort into the signals analysis because the computed outcomes would be for entertainment purposes only.
What truly sets this app apart from any others is that Maemo/MeeGo devices are really the only devices on which I think such an app is even possible. Apple would freak out if a 'legit' app tried to muck around with the baseband, never mind that Apple forbids use of anything but the public APIs (which surely don't give undiluted hardware access to the radios). Android apps actually run in a virtual environment, and the system as a whole is not fully open so developers aren't welcome to muck about with the baseband at runtime there either. What about Maemo (MeeGo)? It's possible that I won't have runtime access to the baseband, sure, but I can download the source and provide myself with an interface to it. Having that in my development environment I can fully implement my code and push for community support for new baseband related APIs.
Basically what I'm saying is that this project isn't feasible on Android or iPhone; there may be show stoppers even on Maemo/MeeGo, but at least there's a path to follow and a realistic possibility to get this app on the Ovi Store.
I'm not announcing the app just yet, but like my other works in progress I want to be able to talk about this publicly while working on it.
Code-named 'Grub', this application will repurpose the GSM/UMTS air interface (radio) of the N900 to provide an augmented reality service that is both entertaining and useful. It's usefulness will depend greatly on factors that I can't fully predict right now; but I saved my old 'Signals and Systems' text book, as well as the text for 'Communications' so I'll dive into those for a refresher and ensure that usefulness is at least theoretically possible.
Implementing the app is another thing altogether; even if the app's usefulness would be proven so limited that no one would use it for professional reasons, the app would still be a lot of fun. So no matter what my research show, I intend to write the app. If the research shows that it cannot be truly useful then I'll put less effort into the signals analysis because the computed outcomes would be for entertainment purposes only.
What truly sets this app apart from any others is that Maemo/MeeGo devices are really the only devices on which I think such an app is even possible. Apple would freak out if a 'legit' app tried to muck around with the baseband, never mind that Apple forbids use of anything but the public APIs (which surely don't give undiluted hardware access to the radios). Android apps actually run in a virtual environment, and the system as a whole is not fully open so developers aren't welcome to muck about with the baseband at runtime there either. What about Maemo (MeeGo)? It's possible that I won't have runtime access to the baseband, sure, but I can download the source and provide myself with an interface to it. Having that in my development environment I can fully implement my code and push for community support for new baseband related APIs.
Basically what I'm saying is that this project isn't feasible on Android or iPhone; there may be show stoppers even on Maemo/MeeGo, but at least there's a path to follow and a realistic possibility to get this app on the Ovi Store.
Progress begets progress
May/03/2010 03:42 PM
With the Qt SDK beta becoming available, and mostly pen-and-paper work performed so far towards implementing my apps, I've migrated to Qt SDK for development. Nokia's progress on Qt has in turn affected progress here on 'Grasshopper'.
Sadly, the Qt SDK doesn't support Mac OSX (yet?) so I am left either using Windows or Linux. I selected Windows, if only because I need to keep a working Windows virtual machine around for my day-job.
What does this mean? Well, I've made some significant head-way on 'Grasshopper':
On paper, the design is complete. I know every feature that I want to include in version 1 of the software and I have a usable and well thought-out interface designed for every feature. Transitions between the interface elements (ie: how to navigate the app) have been drawn up in such a way that (hopefully) I'll be able to reuse a lot of the design elements for multiple parts of the app.
Now that I'm using the Qt SDK, Im getting into actually coding the darn thing instead of just revising my visual state-machines. The UI is roughly 30% complete and the back-end code stubbed out with a relatively clean interface for implementing the heavy-lifting code. I do my coding over the weekends, and expect to have an initial version of my UI functioning (without back-end data loads and stores) by the end of this upcoming weekend. That is very soon. I went from a solid idea on paper to a partially working prototype in one weekend, and will have a fully functional demo of the UI in a second weekend of work. Linking in the back-end data support will likely take a couple weekends as well, giving me an estimated one month before my first alpha release is compiled and running.
Once I get to beta I'll post the project's real name and some teaser videos - and possibly distribute a version for testing and feedback before finalizing and posting the app to the Ovi store.
Qt is fantastic - I'm really happy to be working with it. If development proceeds this easily for 'Locust' I'll be very happy indeed :)
-jared
Sadly, the Qt SDK doesn't support Mac OSX (yet?) so I am left either using Windows or Linux. I selected Windows, if only because I need to keep a working Windows virtual machine around for my day-job.
What does this mean? Well, I've made some significant head-way on 'Grasshopper':
On paper, the design is complete. I know every feature that I want to include in version 1 of the software and I have a usable and well thought-out interface designed for every feature. Transitions between the interface elements (ie: how to navigate the app) have been drawn up in such a way that (hopefully) I'll be able to reuse a lot of the design elements for multiple parts of the app.
Now that I'm using the Qt SDK, Im getting into actually coding the darn thing instead of just revising my visual state-machines. The UI is roughly 30% complete and the back-end code stubbed out with a relatively clean interface for implementing the heavy-lifting code. I do my coding over the weekends, and expect to have an initial version of my UI functioning (without back-end data loads and stores) by the end of this upcoming weekend. That is very soon. I went from a solid idea on paper to a partially working prototype in one weekend, and will have a fully functional demo of the UI in a second weekend of work. Linking in the back-end data support will likely take a couple weekends as well, giving me an estimated one month before my first alpha release is compiled and running.
Once I get to beta I'll post the project's real name and some teaser videos - and possibly distribute a version for testing and feedback before finalizing and posting the app to the Ovi store.
Qt is fantastic - I'm really happy to be working with it. If development proceeds this easily for 'Locust' I'll be very happy indeed :)
-jared