How can we better support the distriqt extensions?

I'm not sure what the full capabilities of user voice are but I've always thought your implementation was severely lacking content, making it pretty useless.

e.g. The extensions area only includes info regarding 3 extensions.

What I think would be very useful to both Distriqt and users is an area where you can select a particular extension (and list all your extensions) and have searchable content which includes tips, faqs, questions asked and answered, i.e. a forum of some sort.

As far as I can see GitHub has no search functionality so if I run into a problem that I cannot resolve the first step is to contact Distriqt. I also think it's important to only have one location to go to for information. i.e. Don't use Github for reporting one kind of issue and another area for general info. It's confusing.

Having the community help resolve other peoples questions I imagine would cut down your time in answering the same issues etc. To encourage users to contribute perhaps implement a points system for correct answers. (similar to stack overflow). The points then being used towards discounts on future ANE purchases.

We need complex and powerful ANEs. And not only for mobile platforms!

We would like to see OpenCV extensions, computer vision libraries and other features for working with images and videos (camera, live streaming, local and remote files).

Also we want to use extensions that improve performance and provide new possibilities like easy working with HID, USB/COM ports, external devices and so on. Also useful features: new video and image formats and codecs support to use it with Stage3D and classic DisplayList.

A video ANE for live streaming and proper video playback for Android an iOS would be exactly what we are looking for. I'm working for a video surveillance company specialized in CCTV and IP based video solutions and we are currently expanding our product range to mobile platforms.

Guys, it's not about what new extensions you want, but how to help Michael having better support for it's products

michaelarchbold - I think what Infin8 said is pretty good example. A kind of forum would be much appreciated - this way people can get help from others who have the know-how. Those problems/solutions could be converted into kind of articles about how to use specific extension, what are the best practices and what are the problems you can face.

Another cool thing of forum-like format is that there will be people which will actively participate in it and would moderate it's content for free. A real community would save you time answering non-experienced users, and would help you focus on features development and complex problem solving.

I think it's important what Infin8 said - those extensions to be listed and have some kind of their own space in that forum/web/whatever you call it. Because now, users must browse through several type of pages/documentation/files with code, in order to get an idea of what's really going on and what that extension can do. A more detailed explanation would be appreciated.

We are very happy you still spend time and efforts in developing those extensions, as they are the only real way out of the black hole that is sweeping Flash, and the only bridge to real app development. So keep up the good work and state any kind of way that users can be helpful to you!

Maybe a roadmap for each extension

Is there anyway to piggyback on StackOverflow?  I find it one of the best to get answers through.

would like to get emails about updates (bug fixing, release notes) to my email. but not too many emails, periodic once or twice a month max IF there is something.

you did it in facebook, however, i stopped using facebook.

also your Release notes doesn't include DATES!! so i have no idea how to relate to updates.

maybe release notes per product (ANE) ? i think it will be better organized

also would like to know more stuff, like, is there support for IOS 8? air sdk 15? whats sdk inside?

Please write more simple documentation to extensions.

I'm using milkman's ane files, and their functions are more easy to use. Their documentation pdf is step by step writes everything.

I like the parse.com example. If I had to choose I'd go with stack overflow. I'm sure most devs are already have accounts and if you gave clear instructions to your subscribers on how to sign up for notifications regarding Distriqt ANE questions I'm sure that would get traction pretty quickly. This would also create more awareness for Distriqt ANE's to non customers.

A dedicated forum could have some unique advantages but I think this in itself is fragmentation from the main source of dev info (which in my view is stack overflow).

I think we saw how the airscene.org forum started up but failed to really take off. A great idea but it just isn't the goto place for answers.

Dated release notes and version numbers would also be useful as sleeper suggests.

I also agree with efecomert in that Milkman games do create some great documentation for getting set up but I do understand that this in itself is a big undertaking, especially when you factor in having to update them when things change. Perhaps there is some way of utilising the community here as well, tasking one member to look after the 'Getting Started' tutorials for each ANE. A template could be set up for each tutorial to follow.

Thanks for this up for ane users input.  Another good signal as far as I'm concerned and gives me a comfort level using your ANE's and keeping up with the great work you guys are doing at Distriqt...

1.) Ability to see other ANE users questions / answers for common issues  / problems with specific ANE's -- Im willing to bet you guys get asked the same questions ALL THE TIME about common issues and having access to something similar to how stackoverflow works where users can vote up or down and vote on the best / correct answer sort of maintains itself -- the good answers / responses rise to the top and users can easily find answers themselves.

2.) Ability to have access to user-contributed code snippets for commonly used, basic (or advanced) uses of ANE's.

3.) Categorized resources for people using Flash Builder, Flash Develop or developing natively... maybe through the use of 'tags' on users questions and answers / responses.

In short, I love the stackoverflow model (though I have my own issues with StackOverflows model - generally speaking -- and that has more to do with HOW people use it, not so much the mechanics of it)... its self-service oriented and when users all chip in, it quickly becomes a deep resource of info and solutions that otherwise require a user inundate you all with repetitive questions or scour the web to pull together different resources and figure it out themselves.  I say lets 'pool' our knowledge / experiences and all ride the train together, so to speak!

Thanks Distriqt team!  Keep up the good work and focus on better supporting the ANEs.

Generally, I feel like you're doing very well.  I don't know if you need a huge support infrastructure.  However, I do think the sample code you've produced is fine for me--but it's a bit of a chore for a couple reasons (none of which are show stoppers):
--.as files don't have correct newline/carriage return to look nice in notepad on Windows.
--they're all reliant on flex.

Documentation is otherwise pretty good!

Support via email is great but probably not super manageable from your perspective.

How do I get support on purchaed products?

Its not obvious and I urgently need help.

Purchased both Battery and Camera ANE

Trying to use in Flash Builder 4.7 Flex based app fot IOS & Android

Both are installed in the app correctly.

The Battery one worlks absolutely fine in both.

With the Camera ANE it seems to get confused, do you have any simple flex example apps?

Thanks

Paul

Paul, in the meantime, I recently finally dived into the camera ANE about a week ago for a new project, and if you can elaborate on what you'd like to see in a demo / example I'll take a stab at throwing it together for you to use as a starting point.  

One of my recommendations was for a way to allow users to share bare-bones code examples with each other so hopefully that is a part of the support overhaul they guys are working on over at Distriqt.

The ANEs are good and well documented, but I know first-hand that sometimes you just need a starting point of reference to look at and sink your teeth into.   Im running FB 4.6 premium (still havent upgraded to 4.7 yet) but the mxml and as3 code should work for you.

Thanks and good luck.

just downloaded latest ANE ZIP from GitHub...could be nice to know what version is this ZIP.

the changelog.txt doesn't have numbers/version numbers, also its not compatible with updates in release notes

simply would like to verify that the zip i downloaded is latest version

when i scroll down changelog i found some version 1.42..and release notes latest is 1.39. but latest updates in changelog doesn't even has a number

release notes – native extensions support