<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: uGuideMe from Mobile Excursions</title>
	<atom:link href="http://wiki.museummobile.info/museums-to-go/products-services/uguideme-from-mobile-excursions/feed" rel="self" type="application/rss+xml" />
	<link>http://wiki.museummobile.info</link>
	<description>Media and Technology on the Go</description>
	<lastBuildDate>Mon, 23 Jan 2012 19:39:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: uGuideMe from Mobile Excursions : Museum Media</title>
		<link>http://wiki.museummobile.info/museums-to-go/products-services/uguideme-from-mobile-excursions/comment-page-1#comment-2790</link>
		<dc:creator>uGuideMe from Mobile Excursions : Museum Media</dc:creator>
		<pubDate>Fri, 16 Sep 2011 10:05:24 +0000</pubDate>
		<guid isPermaLink="false">http://wiki.museummobile.info/?page_id=542#comment-2790</guid>
		<description>[...] Guides created by our Partners through our web based content management software (CMS). Read more.. MuseumMobile Wiki: uGuideMe  Category: Mobile Media, museum newsTags: Mobile Excursions &gt; museummobile &gt; [...]</description>
		<content:encoded><![CDATA[<p>[...] Guides created by our Partners through our web based content management software (CMS). Read more.. MuseumMobile Wiki: uGuideMe  Category: Mobile Media, museum newsTags: Mobile Excursions &gt; museummobile &gt; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Shropshire</title>
		<link>http://wiki.museummobile.info/museums-to-go/products-services/uguideme-from-mobile-excursions/comment-page-1#comment-1923</link>
		<dc:creator>Dan Shropshire</dc:creator>
		<pubDate>Thu, 04 Feb 2010 02:55:02 +0000</pubDate>
		<guid isPermaLink="false">http://wiki.museummobile.info/?page_id=542#comment-1923</guid>
		<description>uGuideMe is now available for iPhone and iTouch users in Apple&#039;s App Store.  Serveral examples guides have been posted to the uguideme.com website including an Example Museum Guide and example Scavenger Hunt.  You can find the application at:

http://itunes.apple.com/us/app/uguideme/id343925069?mt=8

or, by simplying going to http://uguideme.com</description>
		<content:encoded><![CDATA[<p>uGuideMe is now available for iPhone and iTouch users in Apple&#8217;s App Store.  Serveral examples guides have been posted to the uguideme.com website including an Example Museum Guide and example Scavenger Hunt.  You can find the application at:</p>
<p><a href="http://itunes.apple.com/us/app/uguideme/id343925069?mt=8" rel="nofollow">http://itunes.apple.com/us/app/uguideme/id343925069?mt=8</a></p>
<p>or, by simplying going to <a href="http://uguideme.com" rel="nofollow">http://uguideme.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Shropshire</title>
		<link>http://wiki.museummobile.info/museums-to-go/products-services/uguideme-from-mobile-excursions/comment-page-1#comment-1153</link>
		<dc:creator>Dan Shropshire</dc:creator>
		<pubDate>Fri, 06 Nov 2009 00:29:14 +0000</pubDate>
		<guid isPermaLink="false">http://wiki.museummobile.info/?page_id=542#comment-1153</guid>
		<description>I like this line of thinking.  We&#039;d certainly entertain an open architecture like you describe above and I&#039;d especially like to hear more direct feedback from museum developers.  There are some attractive benefits of such an approach for the end user, the content providers, and us.  The trick to this approach is to figure out how to allow access to the code, maintain configuration management and control of the code, coordinate changes to our Guide builder software, and finally how to coordinate releases.  For instance, this would become challenging if two independent programmers were working on the same module within the code, but modifying it for different conflicting reasons.  There are tools like CVS, or RCS which would help manage this type of approach, but without a system designer this could become a bit chaotic.  Perhaps a better approach is a highbred approach whereas a museum advisory board makes recommendations on desired improvements / additions, the general community is then asked to provide software solutions, and then we, Mobile Excursions, integrate those solutions into the final product for testing and release.  In this way, the product is still being supported by the community, but revision control, management, and system engineering is still under the control of a single entity.  In that way, continuity of the code is still kept intact.  I&#039;d be interested to hear comments as to this approach.

Regarding the time commitment needed to build a tour in the app, the time commitment is in creating the content, be it text, audio, video etc.  However, as I think I mentioned in a previous post, this is time that museums, zoo, etc. are likely to spend regardless of what platform they choose as their host.  Once this content is done, it literally takes less than an afternoon to place this content into the guide.  After that, your guide is ready for your patrons and editing the Guide is even easier and less time consuming.  I understand that there is work involved in determining what Guides you want to create, and what the content is you want to place in the Guides, but the actual process of creation and maintenance is completely manageable.  If an art piece changes locations, you can simply drop and drag it onto the new location the map.  If you&#039;d like to update the audio for an exhibit, simply delete the old one and upload the new one.  As soon as it&#039;s saved, the Guide is available to the public and the public is alerted to the fact that there&#039;s a new Guide available.  We understand that time consuming maintenance is one of the major drawbacks of a proprietary solution.  So in response, we&#039;ve really tried to make the interface as simple and time efficient as possible for our users.</description>
		<content:encoded><![CDATA[<p>I like this line of thinking.  We&#8217;d certainly entertain an open architecture like you describe above and I&#8217;d especially like to hear more direct feedback from museum developers.  There are some attractive benefits of such an approach for the end user, the content providers, and us.  The trick to this approach is to figure out how to allow access to the code, maintain configuration management and control of the code, coordinate changes to our Guide builder software, and finally how to coordinate releases.  For instance, this would become challenging if two independent programmers were working on the same module within the code, but modifying it for different conflicting reasons.  There are tools like CVS, or RCS which would help manage this type of approach, but without a system designer this could become a bit chaotic.  Perhaps a better approach is a highbred approach whereas a museum advisory board makes recommendations on desired improvements / additions, the general community is then asked to provide software solutions, and then we, Mobile Excursions, integrate those solutions into the final product for testing and release.  In this way, the product is still being supported by the community, but revision control, management, and system engineering is still under the control of a single entity.  In that way, continuity of the code is still kept intact.  I&#8217;d be interested to hear comments as to this approach.</p>
<p>Regarding the time commitment needed to build a tour in the app, the time commitment is in creating the content, be it text, audio, video etc.  However, as I think I mentioned in a previous post, this is time that museums, zoo, etc. are likely to spend regardless of what platform they choose as their host.  Once this content is done, it literally takes less than an afternoon to place this content into the guide.  After that, your guide is ready for your patrons and editing the Guide is even easier and less time consuming.  I understand that there is work involved in determining what Guides you want to create, and what the content is you want to place in the Guides, but the actual process of creation and maintenance is completely manageable.  If an art piece changes locations, you can simply drop and drag it onto the new location the map.  If you&#8217;d like to update the audio for an exhibit, simply delete the old one and upload the new one.  As soon as it&#8217;s saved, the Guide is available to the public and the public is alerted to the fact that there&#8217;s a new Guide available.  We understand that time consuming maintenance is one of the major drawbacks of a proprietary solution.  So in response, we&#8217;ve really tried to make the interface as simple and time efficient as possible for our users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nancy Proctor</title>
		<link>http://wiki.museummobile.info/museums-to-go/products-services/uguideme-from-mobile-excursions/comment-page-1#comment-1137</link>
		<dc:creator>Nancy Proctor</dc:creator>
		<pubDate>Fri, 30 Oct 2009 11:09:26 +0000</pubDate>
		<guid isPermaLink="false">http://wiki.museummobile.info/?page_id=542#comment-1137</guid>
		<description>Thanks for taking the time to answer a very difficult time so thoughtfully and carefully!

I like the idea of a museum advisory board very much. Even better, I&#039;d like for museum developers to be able to have very direct input into the development of the product. This would both give us a stake in its success and quality, and reassure us that we have some ability to ensure that it will meet our needs. Although you do not charge museums for use of the platform through an up-front license fee or other, there is still a not insignificant time investment required to build a tour in the app and manage content there. I think we&#039;re all looking for ways of minimizing the risk that all that work will have to be redone on yet another platform should uGuideMe cease to meet our needs. We barely have the time and resources to get our work done once, let alone redo it periodically because new platforms aren&#039;t maintained or developed. This, to me, is the great attraction of opensource: that museums can to a greater degree be masters of their destiny using products developed collaboratively by the community. Also, more heads are usually better than one. Is there room to make the &#039;opensource mentality&#039; you have mentioned more tangible, by having a developers&#039; forum or similar where museums can create optional functions or plug-ins on the uGuideMe platform and share them at no additional charge with their museum colleagues? Can&#039;t this be a win-win: the product is enhanced at no additional cost to Mobile Excursions, the museums have more control over their destiny, and a greater stake in sticking with your platform?</description>
		<content:encoded><![CDATA[<p>Thanks for taking the time to answer a very difficult time so thoughtfully and carefully!</p>
<p>I like the idea of a museum advisory board very much. Even better, I&#8217;d like for museum developers to be able to have very direct input into the development of the product. This would both give us a stake in its success and quality, and reassure us that we have some ability to ensure that it will meet our needs. Although you do not charge museums for use of the platform through an up-front license fee or other, there is still a not insignificant time investment required to build a tour in the app and manage content there. I think we&#8217;re all looking for ways of minimizing the risk that all that work will have to be redone on yet another platform should uGuideMe cease to meet our needs. We barely have the time and resources to get our work done once, let alone redo it periodically because new platforms aren&#8217;t maintained or developed. This, to me, is the great attraction of opensource: that museums can to a greater degree be masters of their destiny using products developed collaboratively by the community. Also, more heads are usually better than one. Is there room to make the &#8216;opensource mentality&#8217; you have mentioned more tangible, by having a developers&#8217; forum or similar where museums can create optional functions or plug-ins on the uGuideMe platform and share them at no additional charge with their museum colleagues? Can&#8217;t this be a win-win: the product is enhanced at no additional cost to Mobile Excursions, the museums have more control over their destiny, and a greater stake in sticking with your platform?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Shropshire</title>
		<link>http://wiki.museummobile.info/museums-to-go/products-services/uguideme-from-mobile-excursions/comment-page-1#comment-1129</link>
		<dc:creator>Dan Shropshire</dc:creator>
		<pubDate>Tue, 27 Oct 2009 15:43:36 +0000</pubDate>
		<guid isPermaLink="false">http://wiki.museummobile.info/?page_id=542#comment-1129</guid>
		<description>Future investment into product development is funded by application sales revenue as well as internal investment.  The idea is to work with our industry partners to create great Guides that will generate a real excitement and desire for the platform, and in turn generate revenue for future investment.  i.e.  If attractions support the product, the product will be supported.  Our initial plan is to put as much of that funding as possible into the improvement and expansion of uGuideMe.  From a software standpoint, the architecture of uGuideMe has been designed to be very flexible and open such that major software changes are unnecessary.  Minor mods and tweaks can certainly be handled with the revenue generated by app sales.  We do have larger planned releases to follow our initial deployment, but these are funded by internal sources.

Regarding assurances, as you all know, there&#039;s no guarantee with any product, even open source, that it will always be supported.  In fact, when I worked in industry, we were very concerned about putting our eggs into the open source basket because there was no single person, or company, accountable for its support and maintenance.  However, in the case of Mobile Excursions, there are several aspects of our business model which should make our clients more comfortable.  (1)  We are a company and have people dedicated to the success of this venture.  (2)  The uGuideMe infrastructure doesn&#039;t cost much to maintain.  Our overall operating expenses are very low so continued operation of the program is very achievable even with rapid growth.  (3)  The amount of time and effort to create a Guide on uGuideMe is minimal.  There is no &quot;major investment&quot; by our partners in uGuideMe proprietary software.  Our partners own their own content, and they control their own content.  uGuideMe simply packages all of this content up and provides it to the user in a great handheld package.  Once the content is assembled, the actual time necessary to create the Guide is less than 2 hours.  And, if desired, all of this content can be easily repurposed…it&#039;s not wasted effort.  (4)  Finally, and very importantly, we actively seek user and partner feedback to make our products and services better.  This is part of ensuring that partner needs will be incorporated into the design.  In fact, we&#039;ve recently toyed with the idea of assembling a committee of museum experts to provide design advice and suggestions regarding future enhancements to the uGuideMe platform.  I&#039;d be interested to see what this community thought of that plan and whether or not there would be interest in being a member.</description>
		<content:encoded><![CDATA[<p>Future investment into product development is funded by application sales revenue as well as internal investment.  The idea is to work with our industry partners to create great Guides that will generate a real excitement and desire for the platform, and in turn generate revenue for future investment.  i.e.  If attractions support the product, the product will be supported.  Our initial plan is to put as much of that funding as possible into the improvement and expansion of uGuideMe.  From a software standpoint, the architecture of uGuideMe has been designed to be very flexible and open such that major software changes are unnecessary.  Minor mods and tweaks can certainly be handled with the revenue generated by app sales.  We do have larger planned releases to follow our initial deployment, but these are funded by internal sources.</p>
<p>Regarding assurances, as you all know, there&#8217;s no guarantee with any product, even open source, that it will always be supported.  In fact, when I worked in industry, we were very concerned about putting our eggs into the open source basket because there was no single person, or company, accountable for its support and maintenance.  However, in the case of Mobile Excursions, there are several aspects of our business model which should make our clients more comfortable.  (1)  We are a company and have people dedicated to the success of this venture.  (2)  The uGuideMe infrastructure doesn&#8217;t cost much to maintain.  Our overall operating expenses are very low so continued operation of the program is very achievable even with rapid growth.  (3)  The amount of time and effort to create a Guide on uGuideMe is minimal.  There is no &#8220;major investment&#8221; by our partners in uGuideMe proprietary software.  Our partners own their own content, and they control their own content.  uGuideMe simply packages all of this content up and provides it to the user in a great handheld package.  Once the content is assembled, the actual time necessary to create the Guide is less than 2 hours.  And, if desired, all of this content can be easily repurposed…it&#8217;s not wasted effort.  (4)  Finally, and very importantly, we actively seek user and partner feedback to make our products and services better.  This is part of ensuring that partner needs will be incorporated into the design.  In fact, we&#8217;ve recently toyed with the idea of assembling a committee of museum experts to provide design advice and suggestions regarding future enhancements to the uGuideMe platform.  I&#8217;d be interested to see what this community thought of that plan and whether or not there would be interest in being a member.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MuseumMobile Wiki &#187; Fresh From Twitter today</title>
		<link>http://wiki.museummobile.info/museums-to-go/products-services/uguideme-from-mobile-excursions/comment-page-1#comment-1128</link>
		<dc:creator>MuseumMobile Wiki &#187; Fresh From Twitter today</dc:creator>
		<pubDate>Tue, 27 Oct 2009 12:54:41 +0000</pubDate>
		<guid isPermaLink="false">http://wiki.museummobile.info/?page_id=542#comment-1128</guid>
		<description>[...] the provider: Q&amp;A about UGuideMe iPhone app for museum tours on Museum Mobile&#8217;s wiki: http://is.gd/4EesL #mtogo    fresh, twitter   &#171; Fresh From Twitter [...]</description>
		<content:encoded><![CDATA[<p>[...] the provider: Q&amp;A about UGuideMe iPhone app for museum tours on Museum Mobile&#8217;s wiki: <a href="http://is.gd/4EesL" rel="nofollow">http://is.gd/4EesL</a> #mtogo    fresh, twitter   &laquo; Fresh From Twitter [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nancy Proctor</title>
		<link>http://wiki.museummobile.info/museums-to-go/products-services/uguideme-from-mobile-excursions/comment-page-1#comment-1127</link>
		<dc:creator>Nancy Proctor</dc:creator>
		<pubDate>Tue, 27 Oct 2009 12:53:02 +0000</pubDate>
		<guid isPermaLink="false">http://wiki.museummobile.info/?page_id=542#comment-1127</guid>
		<description>What about ongoing investment in the development of the product: who pays for that? How can museums be assured that the platform will continue to meet their needs in future, after they&#039;ve invested all the time &amp; effort to put their content into your system? We&#039;ve been stuck all too often with proprietary platforms that the vendor can&#039;t afford to keep up to date - hence the great popularity of opensource platforms.</description>
		<content:encoded><![CDATA[<p>What about ongoing investment in the development of the product: who pays for that? How can museums be assured that the platform will continue to meet their needs in future, after they&#8217;ve invested all the time &#038; effort to put their content into your system? We&#8217;ve been stuck all too often with proprietary platforms that the vendor can&#8217;t afford to keep up to date &#8211; hence the great popularity of opensource platforms.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Shropshire</title>
		<link>http://wiki.museummobile.info/museums-to-go/products-services/uguideme-from-mobile-excursions/comment-page-1#comment-1126</link>
		<dc:creator>Dan Shropshire</dc:creator>
		<pubDate>Tue, 27 Oct 2009 12:23:47 +0000</pubDate>
		<guid isPermaLink="false">http://wiki.museummobile.info/?page_id=542#comment-1126</guid>
		<description>From a Museum standpoint, uGuideMe is more of a service than a product.  There is no cost for Attractions to create and post Guides.  The uGuideMe application costs mobile phone users $1.99, but once they have the application installed, users have access to all of the Guides available on the uGuideMe.com website.  In addition, attractions can choose to charge for the Guides they create, in which case they get a majority of the profit, or they can choose to give them away for free.</description>
		<content:encoded><![CDATA[<p>From a Museum standpoint, uGuideMe is more of a service than a product.  There is no cost for Attractions to create and post Guides.  The uGuideMe application costs mobile phone users $1.99, but once they have the application installed, users have access to all of the Guides available on the uGuideMe.com website.  In addition, attractions can choose to charge for the Guides they create, in which case they get a majority of the profit, or they can choose to give them away for free.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nancy Proctor</title>
		<link>http://wiki.museummobile.info/museums-to-go/products-services/uguideme-from-mobile-excursions/comment-page-1#comment-1125</link>
		<dc:creator>Nancy Proctor</dc:creator>
		<pubDate>Tue, 27 Oct 2009 11:55:35 +0000</pubDate>
		<guid isPermaLink="false">http://wiki.museummobile.info/?page_id=542#comment-1125</guid>
		<description>What is the business model for this product? How is it paid for, and by whom?</description>
		<content:encoded><![CDATA[<p>What is the business model for this product? How is it paid for, and by whom?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MuseumMobile Wiki &#187; Fresh From Twitter today</title>
		<link>http://wiki.museummobile.info/museums-to-go/products-services/uguideme-from-mobile-excursions/comment-page-1#comment-1118</link>
		<dc:creator>MuseumMobile Wiki &#187; Fresh From Twitter today</dc:creator>
		<pubDate>Sat, 24 Oct 2009 02:06:47 +0000</pubDate>
		<guid isPermaLink="false">http://wiki.museummobile.info/?page_id=542#comment-1118</guid>
		<description>[...] stuff on http://MuseumMobile.info &#8211; uGuideMe museum tour app http://bit.ly/3tESfB &amp; Int&#8217;l Mobile Survey http://bit.ly/2NuLl3 #mtogo 2009 International Survey of the use, [...]</description>
		<content:encoded><![CDATA[<p>[...] stuff on <a href="http://MuseumMobile.info" rel="nofollow">http://MuseumMobile.info</a> &#8211; uGuideMe museum tour app <a href="http://bit.ly/3tESfB" rel="nofollow">http://bit.ly/3tESfB</a> &amp; Int&#8217;l Mobile Survey <a href="http://bit.ly/2NuLl3" rel="nofollow">http://bit.ly/2NuLl3</a> #mtogo 2009 International Survey of the use, [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

