Comments on: Observations: Mobile applications development http://www.socialbrite.org/2009/07/05/observations-mobile-applications-development/ Social tools for social change Thu, 02 Sep 2010 10:30:47 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: kiwanja http://www.socialbrite.org/2009/07/05/observations-mobile-applications-development/comment-page-1/#comment-224 kiwanja Mon, 06 Jul 2009 12:14:23 +0000 http://www.socialbrite.org/?p=1909#comment-224 Hi Rob Thanks for the link. Very helpful. I agree that it makes sense to have an understanding of the open sourcing process. For me, I was expecting it to be quite simple, but there were certainly challenges! Good to connect here. Ken Hi Rob

Thanks for the link. Very helpful. I agree that it makes sense to have an understanding of the open sourcing process. For me, I was expecting it to be quite simple, but there were certainly challenges!

Good to connect here.

Ken

]]> By: rob allen http://www.socialbrite.org/2009/07/05/observations-mobile-applications-development/comment-page-1/#comment-216 rob allen Sun, 05 Jul 2009 21:11:18 +0000 http://www.socialbrite.org/?p=1909#comment-216 Hi Ken, I agree that in the real world you have to take a very pragmatic approach to application development and licensing issues definately shouldn't be an obstacle to producing something. That said I would certainly encourage any potential mobile applications developer to get a basic understanding of open source because it probably will prove very useful for them in the future - One of the best introductions to open source is at <a href="http://en.wikibooks.org/wiki/Open_Source" target="_blank">http://en.wikibooks.org/wiki/Open_Source</a> Hi Ken,

I agree that in the real world you have to take a very pragmatic approach to application development and licensing issues definately shouldn't be an obstacle to producing something.

That said I would certainly encourage any potential mobile applications developer to get a basic understanding of open source because it probably will prove very useful for them in the future – One of the best introductions to open source is at http://en.wikibooks.org/wiki/Open_Source

]]> By: kiwanja http://www.socialbrite.org/2009/07/05/observations-mobile-applications-development/comment-page-1/#comment-215 kiwanja Sun, 05 Jul 2009 18:04:51 +0000 http://www.socialbrite.org/?p=1909#comment-215 Hi Rob I totally agree with much of what you say. However, in our experiences with FrontlineSMS open sourcing was challenging due to some tricky and complex licensing issues which we never expected. Someone like yourself may be well versed in open sourcing a project, but for people who don't have that knowledge I'd say you're better off concentrating on building something that works and has potential in the field, before you end up spending a lot of time (like we had to) figuring out open source licenses.There's a lot of focus around open source and mobile right now - I posted more of my thoughts on this here: <a href="http://www.kiwanja.net/blog/2009/06/focus-on-the-users-and-all-else-will-follow/" target="_blank">http://www.kiwanja.net/blog/2009/06/focus-on-the-...</a> Ken Hi Rob

I totally agree with much of what you say. However, in our experiences with FrontlineSMS open sourcing was challenging due to some tricky and complex licensing issues which we never expected. Someone like yourself may be well versed in open sourcing a project, but for people who don't have that knowledge I'd say you're better off concentrating on building something that works and has potential in the field, before you end up spending a lot of time (like we had to) figuring out open source licenses.There's a lot of focus around open source and mobile right now – I posted more of my thoughts on this here:

http://www.kiwanja.net/blog/2009/06/focus-on-the-...

Ken

]]> By: DavidIsaak http://www.socialbrite.org/2009/07/05/observations-mobile-applications-development/comment-page-1/#comment-211 DavidIsaak Sun, 05 Jul 2009 13:01:40 +0000 http://www.socialbrite.org/?p=1909#comment-211 I just returned from presenting mobile ICT to several audiences. The hearerswere all expecting an explanation of the latest technology and recommendations for specific tools for development program deployment in the field. they received neither. Instead, after a brief intro, it involved more of what Ken has more eloquently (and once again, more succinctly) described. The tool selection is one of the last activities after the requirements and context is not only understood, but more or less agreed upon by the stakeholders. This is exasperatingly difficult to do, but this "hard" work must be done prior to deployment. I work on mutual understanding and agreement until I see those faces are nodding up and down in agreement. Then, based on cost and schedule, decide when to break it off and either proceed or abandon in favor of a new direction, i.e. "hitting the wall". I just returned from presenting mobile ICT to several audiences. The hearerswere all expecting an explanation of the latest technology and recommendations for specific tools for development program deployment in the field. they received neither. Instead, after a brief intro, it involved more of what Ken has more eloquently (and once again, more succinctly) described. The tool selection is one of the last activities after the requirements and context is not only understood, but more or less agreed upon by the stakeholders. This is exasperatingly difficult to do, but this "hard" work must be done prior to deployment. I work on mutual understanding and agreement until I see those faces are nodding up and down in agreement. Then, based on cost and schedule, decide when to break it off and either proceed or abandon in favor of a new direction, i.e. "hitting the wall".

]]> By: rob allen http://www.socialbrite.org/2009/07/05/observations-mobile-applications-development/comment-page-1/#comment-209 rob allen Sun, 05 Jul 2009 11:39:36 +0000 http://www.socialbrite.org/?p=1909#comment-209 Don't waste time or energy thinking too much about the open sourcing process (if you decide to go that route) until you know you have something worth open sourcing? 1. If you put your project out there (open source) from the beginning there is for more chance of early collabration (& by the why - it's not tricky unless you want to make it tricky - just stick a GPL v3 license on it and put your code for download on sourceforge - that's usually it). 2. You will need source code control - why not use sourceforges SVN 3. Open source is more attractive to funders 4. It is easier to promote your idea if there is already something for people to look at rather than just an idea you are working on - it shows you are serious 5. You either want it to be open source or not - why beat around the bush Don't waste time or energy thinking too much about the open sourcing process (if you decide to go that route) until you know you have something worth open sourcing?

1. If you put your project out there (open source) from the beginning there is for more chance of early collabration (& by the why – it's not tricky unless you want to make it tricky – just stick a GPL v3 license on it and put your code for download on sourceforge – that's usually it).
2. You will need source code control – why not use sourceforges SVN
3. Open source is more attractive to funders
4. It is easier to promote your idea if there is already something for people to look at rather than just an idea you are working on – it shows you are serious
5. You either want it to be open source or not – why beat around the bush

]]>