<div dir="ltr"><div>Hi,</div><div><br></div><div>Thanks for your suggestions. <br></div><div>To optimize the process and avoid mail pollution, if you want to suggest some improvements, please open an issue <a href="https://github.com/llaske/sugarizer/issues/">here</a> (one by suggestion) and wait for our reply.</div><div><br></div><div>However, to complete other answers from the list, I think that before doing suggestions you should take in consideration few things about Sugar/Sugarizer <br></div><div>- It's targeted for children between 6 and 12, some of them can't read (so we tend to avoid "text") and some of them have never used a computer before (so applying what you think as "usual" icon is not necessarily a good idea).</div><div>- It works both on computer and touch devices so concept of tooltip and cursor are not always appropriate</div><div>- It was thought for children that could have visual disability so a colorful screen is not always the best thing to do</div><div>- We expect that children could focus on activities so we tend to avoid multiple windows</div><div><br></div><div>It's nice to have suggestions from beginners. By the way I tend to privilegiate suggestions coming from the field (children, teachers) from suggestions coming from tech guys.</div><div>We're doing software for education, not for tech people.</div><div><br></div><div>Regards.</div><div><br></div><div> Lionel</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mer. 15 mars 2023 à 15:27, MR. OPTIMIST <<a href="mailto:panuj7295@gmail.com">panuj7295@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello Lionel sir and sugar community, <div> I have proposed few changes to Sugarizer UI and I guess few changes are worth adopting. I would be thankful if you once check the document, if you find that changes will actually make difference to the UI and user experience then please give your feedback. So that i can contribute to the proposed changes.</div><div>I have proposed changes and given them numerical identification and also shared the document in editable format so you find any changes can be made please give your feedback.</div><div><br></div><div>Document link:: <a href="https://docs.google.com/document/d/1OwG09QhO8nHJqQmccXhI2sKYx5LnEGaEVoW5rv5BN5Q/edit?usp=sharing" target="_blank">Click me to open !!</a><br></div><div><br></div><div>Thank you. </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 15, 2023 at 1:22 AM James Cameron <<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thanks. I looked at the document previously and saw some of the proposed changes are immediately suitable for being proposed in our usual workflow, but I'm not the person who will be approving the changes, so I won't be specific about them.<br> <br> I am maintainer of the GTK Implode activity, but your changes are for the Sugarizer version.<br> <br> On Tue, Mar 14, 2023 at 02:03:05AM +0530, MR. OPTIMIST wrote:<br> > Hello James Cameron sir, <br> > Thanks for your feedback. I agree with you that sugar is an<br> > educational platform and it does not look like flooding things on the internet<br> > but user experience plays a vital role in any of the platforms be it commercial<br> > or non profitable. Just a simple question: will you use a phone with no broken<br> > or no display, Same is user experience. So if we can improve, why shouldn't we<br> > improve ? <br> > <br> > Also I would be thankful if you kindly let me know which of the proposed<br> > changes seems to reasonable So that I can further proceed with further<br> > contribution.<br> > Proposed document link:-[1]click me to open<br> > <br> > On Tue, Mar 14, 2023 at 1:29 AM James Cameron <[2]<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>> wrote:<br> > <br> > Some of the changes proposed seem reasonable, but they aren't in the right<br> > form for review; they need to be pull requests against the appropriate<br> > repository.<br> > <br> > I don't think we're using the older design review committee process any<br> > longer, and it should not be revived. The pull request review process is<br> > sufficient. In the case of Sugarizer, that's the process that Lionel has<br> > preferred.<br> > <br> > However, as someone who works in science research, the proposal does not<br> > seem to have been researched, but is rather a collection of ideas that<br> > would be suitable for changing Sugarizer using A/B testing for the goal of<br> > increasing engagement and selling advertising. Neither of these are<br> > intended, it's an educational project. Sugar and Sugarizer don't have to<br> > look like everything else on the internet, and starting with that premise<br> > is an error.<br> > <br> > On Mon, Mar 13, 2023 at 04:35:27PM +0530, MR. OPTIMIST wrote:<br> > > Thanks Alex Sir,<br> > > Your response to email is very much appreciated.<br> > Sorry<br> > > for the late reply.<br> > ><br> > > I love to mention that I have used sugarizer for many days and I also<br> > know that<br> > > its UI has been designed with the vision that it's gonna be used by<br> > childrens.<br> > > My point is that sugarizer was developed back in 2013 and the internet<br> > > revolution at the time was very less in comparison to 2023. The UI and Ux<br> > terms<br> > > were not that considerable at that time and everyone didn't had access to<br> > the<br> > > mobile phones and internet, But as of now in 2023 the childrens from 1 or<br> > even<br> > > less than that start using technical devices and the UX is what first<br> > thing<br> > > that they interact with like games and other applications.So the UI of<br> > > sugarizer is not matching with the need of today's generation which<br> > reduces the<br> > > user interest (research) to use the platform. So my point is we can work<br> > to<br> > > enhance its UI to meet today's need and increase the interaction time of<br> > the<br> > > users of our product.<br> > ><br> > > Considering my skills, I'm a second year engineering student and a self<br> > > learner, I have done multiple projects on AI based applications and<br> > developed 2<br> > > websites as of now. To authenticate my words hereby i have listed all my<br> > > projects in my github account and link of my github account is:- <br> > > [1] [3]<a href="https://www.github/Anujverma89" rel="noreferrer" target="_blank">https://www.github/Anujverma89</a><br> > ><br> > > Considering what part of the product and UI can be modified to give new<br> > user<br> > > experience, I have done research and explained it in the given pdf you<br> > can view<br> > > it thoroughly.<br> > > Here is the link :-<br> > > [2]Click me to open !! <br> > ><br> > > Your suggestions on changeable topics(UI) will be highly appreciated !! <br> > > Thank You..<br> > ><br> > > On Sat, Mar 11, 2023 at 12:18 AM Alex Perez <[3][4]<a href="mailto:aperez@alexperez.com" target="_blank">aperez@alexperez.com</a>><br> > wrote:<br> > ><br> > > Anuj,<br> > ><br> > > I appreciate your enthusiasm, and welcome. Before any UI re-design<br> > would be<br> > > considered, we would require detailed written analysis of what the<br> > goals<br> > > are for such a re-design, what's "wrong" with the current design, and<br> > what<br> > > your qualifications are for making what are largely subjective<br> > changes.<br> > > While everyone has opinions on UI design, engineers are often<br> > infamous for<br> > > designing awful user interfaces. Please share with us what sorts<br> > > qualifications you possess that would qualify you to make UI design<br> > changes<br> > > to Sugar/Sugarizer.<br> > ><br> > > Have you ever used Sugar for more than a few hours, or a day? If so,<br> > which<br> > > elements do you feel should be changed? If you have not used Sugar<br> > > extensively, I would argue that you likely lack sufficient experience<br> > to<br> > > propose such changes.<br> > ><br> > > The Sugar/Sugarizer UI was primarily designed for children of a<br> > specific<br> > > age range. Almost all design decisions stem from that basic premise.<br> > Have<br> > > you considered this?<br> > ><br> > > Regards,<br> > > Alex Perez<br> > ><br> > > MR. OPTIMIST wrote on 3/10/23 10:24 AM:<br> > ><br> > > Hello everyone !<br> > > I am Anuj Verma from Maharashtra, India majoring<br> > in<br> > > computer science and engineering. I have worked in<br> > multiple projects<br> > > and web applications including AI projects.<br> > > I have checked the sugarizer, it's pretty good but I believe it's<br> > UI<br> > > can be improved. Like we <br> > > can add links to words as well as icons, we can improve icons as<br> > well<br> > > which is less user friendly(in my opinion).I have experience of<br> > working<br> > > with many projects but have not worked on open source yet. I'm<br> > > writing to seek further comments and be open to constructive<br> > feedback<br> > > and criticism. Your response to this mail will be highly<br> > appreciated.<br> > ><br> > > References:<br> > ><br> > > [1] [5]<a href="https://www.github/Anujverma89" rel="noreferrer" target="_blank">https://www.github/Anujverma89</a><br> > > [2] [6]<a href="https://docs.google.com/document/d/" rel="noreferrer" target="_blank">https://docs.google.com/document/d/</a><br> > 1OwG09QhO8nHJqQmccXhI2sKYx5LnEGaEVoW5rv5BN5Q/edit?usp=sharing<br> > > [3] mailto:[7]<a href="mailto:aperez@alexperez.com" target="_blank">aperez@alexperez.com</a><br> > <br> > > _______________________________________________<br> > > Sugar-devel mailing list<br> > > [8]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br> > > [9]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br> > <br> > _______________________________________________<br> > Sugar-devel mailing list<br> > [10]<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br> > [11]<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br> > <br> > References:<br> > <br> > [1] <a href="https://docs.google.com/document/d/1OwG09QhO8nHJqQmccXhI2sKYx5LnEGaEVoW5rv5BN5Q/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1OwG09QhO8nHJqQmccXhI2sKYx5LnEGaEVoW5rv5BN5Q/edit?usp=sharing</a><br> > [2] mailto:<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a><br> > [3] <a href="https://www.github/Anujverma89" rel="noreferrer" target="_blank">https://www.github/Anujverma89</a><br> > [4] mailto:<a href="mailto:aperez@alexperez.com" target="_blank">aperez@alexperez.com</a><br> > [5] <a href="https://www.github/Anujverma89" rel="noreferrer" target="_blank">https://www.github/Anujverma89</a><br> > [6] <a href="https://docs.google.com/document/d/1OwG09QhO8nHJqQmccXhI2sKYx5LnEGaEVoW5rv5BN5Q/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1OwG09QhO8nHJqQmccXhI2sKYx5LnEGaEVoW5rv5BN5Q/edit?usp=sharing</a><br> > [7] mailto:<a href="mailto:aperez@alexperez.com" target="_blank">aperez@alexperez.com</a><br> > [8] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br> > [9] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br> > [10] mailto:<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br> > [11] <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br> </blockquote></div> </blockquote></div>