Hi!
Welcome to this new forum on community activities. The idea is to discuss how we can evolve the MoSync developer community. I recently got appointed to work with our community and it would be great to get feedback! You are most welcome to post ideas on activities you would like to see ahead or any other topic related to our community. You can also drop me a mail to tomas dot uppgard at mosync dot com.
Cheers!
Tomas
Awesome job!
Please read everything I have posted on these forums.
Also have a look at the code.google.com/p/mosync site where the issue tracker is...
the community tried or tries to give back there, but if they feel they aren't heard they will dry up...
Here's what your task list probably looks like:
1) Answer all unanswered questions on forum
2) Update all outstanding tickets/issues on the code.google.com site
3) Go through the website as a user and remove unnecessary or duplicate pages.
4) Link up pages to each other on the website that are related so that navigation can flow.
5) Answer and go through ALL questions on stackoverflow.com regarding mosync.
6) Create a tag on stackoverflow for mosync if there isn't already one
7) Answer all questions on stackoverflow regarding mobile cross platform dev etc
Have fun!
Some bonus tasks:
* Try to make it clearer what the company is working on and where things are... I have given some suggestions before so go have a look!
Hi David!
Thanks for your feedback, this is most appreciated! Good suggestions, we will make sure to improve in all of these areas. I will also post more questions to discuss improvements more in detail. Stay tuned.
Cheers!
Tomas
Suggestion: please make one of the forum topics dual purpose, e.g. change "Publishing Your App" section to " Publishing Your App and App Showcase"
We want a place to post our app or screenshots of our app to let people know what we do with MoSync!
Remove the button at the top of the site "Code" , as the people who need that will go through "Dev Center" first. It's just cluttering things up. Also, can't you put the "Jobs" button at the top at the bottom perhaps?
The site has way to many options to click on to read through for a new interested visitor.
Another tip to improve sign up rates on your site:
1) I mentioned this in my first post I think, but please make the password requirements to sign up easier, its way too difficult and time consuming to choose a password causing a high drop off rate of prospective users to sign up for a mosync account. Not making it necessary would be great too. e.g. OpenId :)
Hi David!
Thanks for the suggestions, very good! We will look into these things!
Cheers!
Tomas
Hello,
Here is my contributions
-It’s very important to precise inside the documentation near every functions all the platforms which supports it. For instance
maCreateStore (available on android, iphone...)
Something like that for all functions
-For every nighty builds, please make a list of all new features or bug fixes you’ve done inside this build.
-You must open an gallery of mosync applications and screenshots which are done by developers around the world
Thanks !
Hi Eric!
Thanks for your contributions, good points! We will make sure to address them as fast as we can. App Gallery is in the works, stay tuned!
Cheers!
Tomas
> For every nighty builds, please make a list of all new features or bug fixes you’ve done inside this build.
The list of commits should be viewable on the changelog/checkin log on the source code, namely here: https://github.com/MoSync/MoSync/commits/master (The Commits Button on github)
@Tomas, I see you guys are using some bugtracker? A JIRA system? I see commits with "MOSYNCTWOSIX-495"
Hi! It would be cool to have this list always on the forum or on the download page near all nighty build link.
Hi,
Some more tips:
1) The examples imported in MoSync are getting too much now - you can't find what area you want to find an example for.
Please create folders/categories for different areas, e.g. 3D, User Interfaces, HTML/WEB, API's, Device Features, Full Demo's/Samples
The list is currently too daunting and new guys will be pushed away from playing around because they just want something quick to run but have to look through all the samples to find the full samples/demo's that are interesting.
2) The FacebookDemo should work without a key and should only ask for a key when clicking on a function that requires it. i.e. use the public facebook graph until required for a key. Frustrating to not have a sample just work. Ask for key at runtime even? Insert a link that opens the browser on the PC the sample is running that takes you to your API Key page on facebook.com
Cheers,
David
Hi David!
We have an internal JIRA which we are using. We haven't made that public yet but that is planned for the near future, as in a week or two. The only reason we haven't that public just yet is that we needed to learn and to test the system first. Now we are comfortable with it so it's ready to go live.
Guys,
I am sure you already know about it. Jira is out now and is made public. Just in case, if some people don't know, take a look here.
http://jira.mosync.com/secure/Dashboard.jspa
Cheers,
Abi Waqas