查看完整版本 : Windows 10 Phone 疑已確定採用漢堡菜單

COROLLA2003 2015-4-19 10:13

Why the switch?
Here is why Microsoft wants hamburger menus in Windows 10 for phone

The controversial switch from the ellipsis in Windows Phone 8 to the hamburger menu in Windows 10 for phone was explained by a former, and anonymous, Microsoft employee during a verified Reddit AMA session this week.

While the employee chose not to identify himself, he has been verified by Reddit.

The employee stated he worked as a "design lead" on the new version of Office for Windows Phone but left Microsoft about a year ago. He also discussed and debated the reasons why Microsoft made the switch in a video, along with placing a navigation bar on top. Here is what he wrote during the AMA session:

"Ah yes, the hamburger. So. I've written so much about this (and even made videos) that I'll do my best to summarize."

"Windows Phone's original interaction model put actions on the bottom and navigation on the sides, as swipes. That's not a great pattern for a variety of reasons."

"iOS started with a lot of apps using tabs on the bottom, and over time started aligning more with Android, who put a few key actions on the top, then a "swipe back" pattern for more options. Think of Mail on iOS, how you go into a message, then you can swipe from the left to get back to your inbox."

"Windows Phone was left in an interesting spot. Many of us believed that the old interaction model just wasn't going to work. You can't stick navigation in a horizontal direction. It's part carousel, part "mystery meat navigation" and it just doesn't work. So. We needed to figure out what the new model would be."

"Putting a title bar on the top was the first important step. If you're in Word and you can't see the name of your document, that's not good. So, ok, put a bar across the top. And now you have a bar across the top you can provide a back arrow in the top left to get back to your documents. Awesome."

"Then you put the ribbon in what I called a "palette" or "drawer" on the bottom, and on the top right you can start putting "hero actions." I argued for only one but I'm unsurprised that they ended up with more."

"So there you go, right?"

"Top: <-- Name of document common actions"

"Bottom: Three dots to get the ribbon in palette form."

"The problem is, there's just way too many things on the top bar. For example, you might want to print. How do you do it? Well, you could design a print icon in the top bar. But it's probably not worth it. You could hide it in the ribbon, but that sort of sucks for discoverability."

"And then you notice the top left corner. And you think "Well, tons of Android apps just put everything there. Maybe we could try that?"

"And so it became clear, due to the massive number of features in Office apps, and the extremely tight real estate, and alignment with tablets, that a hamburger was the best overall pattern."

The rest of the Reddit AMA is really fascinating. In short, Microsoft is citing a lot of internal research that highlights two important facts about their decision making in regards to the hamburger menu:
1.People do not use a phone one-handed as much as you may think, especially with large screen phones hitting the market
2.They have explored alternative design models but "Being a special unique snowflake works for art but not design." In other words, alignment with Windows desktop and the rest of the world trumps being different for the sake of being different

Will this end the debate about hamburger menus and adding a top Nav bar? Likely not. However, consumers have shown that this is what they know, research data suggests this works best, and the majority of users will prefer it.

Anyway, you know the drill: Watch the video, read some of the AMA and then come back and share your thoughts

前微軟員工詳解Windows 10 Phone採用漢堡菜單的原因  

昨天一位微軟前雇員在新聞網站 Reddit 上的一次“有問必答(AMA)”活動中解釋了 Windows Phone 8 “省略號式”菜單向 Windows 10 Phone 漢堡菜單過渡的原因。雖然這位前微軟員工選擇匿名,但 Reddit 已核實了他之前的身份。

完美全屏 無法播放?

這位員工稱自己是 Windows Phone 新版 Office 應用的“設計帶頭人”,但他已於一年前離開了微軟。他還通過一則視頻談論並論證了微軟選擇這項過渡以及將導航欄放置於頂部的原因。下面是他在 AMA 環節中寫的話:

引用: 是的,漢堡菜單。我之前寫過太多過於漢堡菜單的內容(甚至還做過視頻),我會盡自己最大努力將這件事總結清楚。
Windows Phone 的最初交互模式是將操作鍵放在頂部,通過橫向滑動的方式進行導航。出於各種原因,這並不是一個很好的模式。
iOS 起步時,有大量應用在屏幕底部使用標簽,後來應用風格開始向安卓靠攏,後者習慣將一些關鍵操作鍵放置於屏幕頂部,接著還有一個呈現更多選項的“滑動返回(swipe back)”模式。想想 iOS 版郵件應用吧,在你進入一條信息中後,你可以從左向右滑動來返回至收件箱。
Windows Phone 的處境很有趣。我們中的許多人相信老式的交互模式已無法有效運行。你不能一直堅守橫向導航方式,這看起來既有些像旋轉木馬,又有點像“mystery meat 導航(指必須將指針放在頁面中指定區域後,隱藏的鏈接才會得以顯現,含貶義)”,它已不能很好滿足操作需求。因此,我們需要想出一種新的交互方式。
將標題欄放在屏幕頂部是重要的第一步。如果你在 Word 中但卻無法看到文檔的標題,那種感覺並不好。因此,在頂部放置一個操作欄。現在你在頂部擁有了一個操作欄之後,你可以在左上角提供一個返回箭頭來返回你的文檔。非常棒。
接著你在屏幕底部放置一個 Ribbon 功能區,也叫“調色板”或“抽屜”。你可以在右上角部位放置“hero actions(關鍵操作)”。我曾建議只放置一個,但他們後來放置了多個。
所以就形成了現在的樣子,頂部是文檔名與一般操作,頂部是調出抽屜式 Ribbon 功能區的省略號圖標。
問題是,頂部操作欄集中了太多東西。舉例來說,你可能想進行打印操作。你會怎麼做?你可能會在頂部標題欄設計一個打印圖標。但這很可能並不值得那麼做。你可能會將之隱藏在 Ribbon 功能區,但由於隱藏性過強,這種方式並不高明。
因此事情現在變得清晰了,由於 Office 應用中包含了大量功能,同時屏幕面積又非常有限,再考慮到與平板看齊後,漢堡菜單就成了最佳整體解決方案。


他們探索了替代設計模型,但“成為一朵獨一無二的雪花那是藝術的追求,而不是設計的追求。”換句話來說,向 Windows 桌面版與其他趨勢看齊最終戰勝了“與眾不同”的想法。


Source wc

[[i] 本帖最後由 COROLLA2003 於 2015-5-1 06:34 AM 編輯 [/i]]

COROLLA2003 2015-4-19 10:16



Regexman 2015-4-19 11:35

[quote]原帖由 [i]COROLLA2003[/i] 於 2015-4-19 10:13 AM 發表 [url=http://www.discuss.com.hk/redirect.php?goto=findpost&pid=414657464&ptid=24583389][img]http://www.discuss.com.hk/images/common/back.gif[/img][/url]
Why the switch?
Here is why Microsoft wants hamburger menus in Windows 10 for phone

The controversial switch from the ellipsis in Windows Phone 8 to the hamburger menu in Windows 10 for phone w ... [/quote]
真正嘅NAV其實喺WP一真存在,就係back button。整Hamburger button 唔係唔好,而係好難單手操作,我諗微軟如果諗到條橋可以用手勢打開Hamburger menu,我相信會冇人再反對

COROLLA2003 2015-4-19 14:11

Will the Start screen and Live Tiles be the next to go?

We saw Hubs go, we saw Panoramas go, we saw the unique user interface of the camera app (with its instant preview) on Windows Phone go, we saw camera buttons go, we even saw the app bar go, leaving precious little of what made Windows Phone Windows Phone.

[img] http://wmpoweruser.com/wp-content/uploads/2015/04/startback_thumb.jpg [/img]

It seems clear to me that the next thing to go will be the Start Screen, composed of Live Tiles. Windows 10 desktop already de-emphasizes Live Tiles, and it would not take much more to abolish them completely.The reason is simple – Microsoft is trying to create a user interface familiar to iOS and Android users, and apparently the stark appearance of Windows Phone is turning them off.

In Jon Bell’s words:

The stark look of Windows Phone seemed to turn off more people than fell in love with it. I know here in this forum we’re all fans but in the mainstream marketing was only one problem.

In addition Microsoft is working on Android app compatibility, and those apps often come with widgets for the home screen, suggesting the unique Windows Phone home screen will not be wanted anymore, and Windows Phone will then be nothing more than Microsoft’s version of Android.


我們在Windows 10 Phone中目睹了Hub(中心)的消失,Panoramas(環形概覽界面)元素的消失,《相機》應用獨特UI的消失,app bar(應用欄)的消失。要知道,正是這一系列珍貴的元素才造就了與眾不同的Windows Phone。 筆者很清楚下一個即將消失的可能就是由動態磁貼組成的開始屏幕了。Windows 10桌面版已經不再強調動態磁貼,完全廢除它們也不會有什麼大礙。原因很簡單——微軟正在試圖構建一種與iOS及安卓類似的用戶界面,顯然Windows Phone鮮明的外觀與微軟預想的設計背道而馳。微軟交互設計師Jon Bell說道:

Windows Phone鮮明的外觀似乎更容易讓人不願接納它而不是喜愛上它。我知道論壇裡的朋友都是WP粉絲,但主流市場才是唯一的問題。

此外微軟目前正在致力於兼容安卓應用的工作,且那些應用通常伴隨著主屏幕的一些小部件,因此獨特的Windows Phone主頁面已無用武之地,Windows Phone也將成為微軟專屬版本的安卓系統。

source wmpu


COROLLA2003 2015-4-19 14:13

竟然, 國內喜愛微軟界面這改變:o


Regexman 2015-4-19 15:04

[quote]原帖由 [i]COROLLA2003[/i] 於 2015-4-19 02:13 PM 發表 [url=http://www.discuss.com.hk/redirect.php?goto=findpost&pid=414679297&ptid=24583389][img]http://www.discuss.com.hk/images/common/back.gif[/img][/url]
竟然, 國內喜愛微軟界面這改變:o

http://i.discuss.com.hk/d/images/r10/androidD.jpg [/quote]

Regexman 2015-4-19 15:06

[quote]原帖由 [i]COROLLA2003[/i] 於 2015-4-19 02:11 PM 發表 [url=http://www.discuss.com.hk/redirect.php?goto=findpost&pid=414679085&ptid=24583389][img]http://www.discuss.com.hk/images/common/back.gif[/img][/url]
Will the Start screen and Live Tiles be the next to go?

We saw Hubs go, we saw Panoramas go, we saw the unique user interface of the camera app (with its instant preview) on Windows Phone go, we saw  ... [/quote]
我覺得作者似係諷刺緊WP對介面嘅一系列改變先咁大膽估MS下一步會放棄Start screen

COROLLA2003 2015-4-19 15:44

[u][color=#003080]【投票活動】: Windows Phone 不主流原因是因為 UI 過於獨特?[/color][/u]


Regexman 2015-4-19 16:40



COROLLA2003 2015-4-19 16:49


不過諗下微軟亦無道理, 因為喜愛的只是wp 用家, 而現在要吸引的是別系統用家。


[[i] 本帖最後由 COROLLA2003 於 2015-4-19 05:18 PM 使用[url=http://www.discuss.com.hk/android][img=100,23]http://i.discuss.com.hk/d/images/r10/androidD.jpg [/img][/url] 編輯 [/i]]

Regexman 2015-4-19 17:22

[quote]原帖由 [i]COROLLA2003[/i] 於 2015-4-19 04:49 PM 發表 [url=http://www.discuss.com.hk/redirect.php?goto=findpost&pid=414694208&ptid=24583389][img]http://www.discuss.com.hk/images/common/back.gif[/img][/url]

不過諗下微軟亦無道理, 因為喜愛的只是wp 用家, 而現在要吸引的是別系統用家。

http://i.discuss.com.hk/d/images/r10/androidD.jpg [/quote]

COROLLA2003 2015-4-19 17:23

[quote]原帖由 [i]Regexman[/i] 於 2015-4-19 05:22 PM 發表 [url=http://www.discuss.com.hk/redirect.php?goto=findpost&pid=414697087&ptid=24583389][img]http://www.discuss.com.hk/images/common/back.gif[/img][/url]但問題就係令其他系統用家卻步嘅係Apps,並非介面 [/quote] 應該兩樣都有, app 就微軟無乜有用辦法。


COROLLA2003 2015-4-19 18:04


自WP7發布後,一段時間內個人對wp的metro很是推崇,但用過一段時間,metro總體來說對多數人來說一是不美觀,二是不實用不易令人接受,metro方塊的信息功能並不重要,只是體現在有限的幾個應用上,但價值並不大,大多數還是充當圖標的功能,並且metro方塊確實很難看,想把方塊擺的好看還是有難度的,反而不如ios固定大小圖標簡單實用。所以當時發了很多帖子說阻礙wp普及的最大就是metro,但是被人狂噴。 metro帶來的扁平化潮流到時被蘋果和安卓學了去,但是,扁平化並非是metro帶來的,在桌面很多軟件界面在metro出來之前就 ​​走小清新扁平界面了。 現在終於看到微軟在wp界面設計上走在正確的軌道上,今後會看到wp很多被粉絲吹牛逼的設計都被放棄。 但是個人認為metro在大屏設備上是比安卓和ios的界面更具實用性,如平板、電視等。 

source aizuliang


Regexman 2015-4-19 18:28

[quote]原帖由 [i]COROLLA2003[/i] 於 2015-4-19 06:04 PM 發表 [url=http://www.discuss.com.hk/redirect.php?goto=findpost&pid=414701451&ptid=24583389][img]http://www.discuss.com.hk/images/common/back.gif[/img][/url]

自WP7發布後,一段時間內個人對wp的metro很是推崇,但用過一段時間,metro總體來說對多數人來說一是不美觀,二是不實用不易令人接受,metro方 ... [/quote]

COROLLA2003 2015-4-19 21:38


    WP:滑動 ≈ 點擊 > 長按
    IOS:滑動 ≈ 點擊 >> 長按

Source pivthon

PJW 2015-4-20 02:46


我公司可能比較特別,有10%既人係用WP嘅,當然大家都有用過或者用緊andorid, ios

PJW 2015-4-20 03:03

[quote]原帖由 [i]COROLLA2003[/i] 於 2015-4-19 06:04 PM 發表 [url=http://mobile.discuss.com.hk/redirect.php?goto=findpost&pid=414701451&ptid=24583389][img]http://mobile.discuss.com.hk/images/common/back.gif[/img][/url]

自WP7發布後,一段時間內個人對wp的metro很是推崇,但用過一段時間,metro總體來說對多數人來說一是不美觀,二是不實用不易令人接受,metro方 ... [/quote]

而且win 10並無放棄live tile,咁樣仲算唔算「走回正確嘅道路」..?

COROLLA2003 2015-4-20 06:36

[quote]原帖由 [i]PJW[/i] 於 2015-4-20 03:03 AM 發表 [url=http://www.discuss.com.hk/redirect.php?goto=findpost&pid=414754943&ptid=24583389][img]http://www.discuss.com.hk/images/common/back.gif[/img][/url]

而且win 10並無放棄live tile,咁樣仲算唔算「走回正確嘅道路」..? [/quote]

這說明了忠實wp用戶與非wp用戶感受不同。 這就是微軟所講的分歧。
靜待微軟怎樣變。 最終成怎樣給用家。

COROLLA2003 2015-4-20 09:29

Another ex-Microsoft engineer talks about how the company develops operating systems

A few days ago we had an ex-Microsoft designer talk about how the company came to its decision to largely replace pivots with the hamburger menu, noting that the decision was supported by a lot of data and was the result of concerted debate and discussion by a lot of very smart people.

Now we have another ex-Microsoft engineer, who works in the Windows team for more than 10 years, offer an insight into how sometimes great ideas turn into pretty bad implementations, or how bad ideas sometimes makes its way through the whole process to end up in shipping products.

The post was spotted elsewhere on the web, which I am not linking to, as he may not want the possibly negative attention. I was able to verify his identity as a long time Microsoft veteran however.

He writes:

I used to be a Windows engineer, and I’ve been in those Meetings.

Usually you have some outgoing and charismatic Program Manager who announces that the feature team has Made a Decision. Ultimately, the Decision is about compromising on the functionality, or the scope, or the timeline, or occasionally the existence of the Feature. The Feature as originally conceived was going to be fast, adaptive, configurable, intuitive, self-documenting, and above all user-friendly. Often the designs are vetted with users and industry partners who get a chance to sign off on the Feature. Don’t look at me like that. At this stage in the product, the next version of Windows was the most awesome thing conceived, take my word for it. During the course of the release, a steady stream of Decisions whittles that down until what is released looks nothing like what was envisioned.

The thing is, that in context and at the time, the Decision doesn’t look bad at all. The Decision is the result of a careful consensus between the PM, the Dev, and the Tester. These engineers have spent hours in meetings weighing their options, evaluating the pros and cons of each, plotting out the likely effects, and ultimately selecting the best among many competing options. (Or possibly the Decision was handed down from upper management; but the result is the same) The process is foolproof and meticulous, and guaranteed to arrive at the best possible outcome for all of the parties in the room.

The problem is who is not in the room. At this stage, often during week four of a six-week milestone, there’s no time to go back out and consult the User. In theory, almost everybody in engineering at Microsoft is an advocate for the User. PMs get inside the User’s head during planning, so the Feature can anticipate their every need. Testers are the first ones to feel the User’s pain when it doesn’t. Management meets with Partners, who are kind-of like users, but with a lot more money and influence. Devs … Devs actually don’t really care about the user. But anyway. In practice, this doesn’t work because nobody in Windows engineering has ever actually met the User. They instead rely on an idealized mental model of a generic user which has attributes assigned to it by higher-paid engineers.

The feature team consult this model and a ouija board and carefully rationalize all of the considerations that led to the Decision. But the Decision is ultimately made from engineering considerations and not user considerations, simply because the User isn’t at the table. It’s extra work to maintain multiple UIs for a product. We don’t have enough time to test multiple configurations. The other guy has higher market share than we do; if we just copy him maybe we will do better. All of these are true, more or less, and all of them are good reasons to support the Decision. But all of them are asked and answered from the perspective of Microsoft.

So on the day of the Meeting, the PM will go on and on about how the Decision benefits the User. They come up with facts that support the Decision. We don’t want to confuse the User with too many options. Only 3% of people used it that way, so clearly it’s okay to remove. Consistency is good for Microsoft, so it must be good for the User. Everybody smiles and nods and agrees this is the best way. The newest to the team, because it just makes so much sense. The veterans, possibly because they secretly know it’s about the engineers and not about the User, but more likely because engineers are inherently lazy. The meeting ends and the Feature has a new direction. It’s a little bit farther from the vision, and maybe little bit worse user experience, but writing software is about compromise. This was a good compromise. It’s not that bad, anyway. It was the best option available. If only the User was there to see it, they’d understand that.

I used to be a Windows engineer. As I watched this video, I suddenly felt like I was back in that Meeting.


兩天前一位前微軟設計師談論了公司是如何決定在Windows Phone中使用漢堡菜單來大幅取代樞軸式UI的,這位設計師稱這個決定得到了大量數據的支持,同時也是設計組共同討論的結果,許多非常聰明的團隊成員都讚同這項決定。 現在又有一位在Windows團隊工作了超過10年的前微軟工程師現身說法,為我們解釋了卓越的創意是如何被糟糕的執行糟蹋的,以及糟糕的創意是如何通過可行性論證並最終成為上市產品的。他寫道:

我曾經是一名Windows工程師,也參加了那些會議。 通常會有一些性格外向且頗具魅力的項目經理宣布,功能團隊已做出了一個決定。最終,這項決定是關於功能性,或者適用範圍,或時間線,偶爾也關於功能去留問題的妥協。最初構想的功能特性是朝以下方面發展的:快速、適應性、可配置性、直觀性、自我記錄,最重要的是用戶友好性。通常情況下這些設計都由具有功能批准權的用戶與合作夥伴進行審查。在這個階段的產品,即下一代Windows系統,是非常了不起的產物,請相信我的話。而在產品發布過程中,一連串的決定不斷對Windows的功能性等各方面進行削減,以至於到正式發佈時,最終產品已與最初構想的產品大相徑庭。問題是,在整個流程中,這些決定看起來並不糟糕。決定是由項目管理團隊、開發人員與測試人員經過仔細審議達成共識後作出的。這些工程師在會議中花了大量時間來權衡他們的選擇、評估每項決定的優缺點、策劃出可能的影響,並最終從多個競爭選項中選出最佳選項。(或者決定也可能由上層管理傳達下來,但結果是一樣的)整個過程是簡單細緻的,同時保證了照顧到會議室中所有團隊觀點後得出的最佳結果。 那麼問題也來了:誰沒有參與到決策會議中來呢?在這個階段,通常時間週期為4到6週,根本沒有時間去諮詢用戶。理論上來說,幾乎所有微軟工程團隊中的成員都算是用戶的代表。項目管理者們在規劃時已經了解了用戶的想法,所以這些功能可以預測他們的每一項需求。測試者最先覺察到用戶的不滿意之處。合作夥伴則有些像用戶,但他們更有錢,同時也更有影響力。至於開發者們,他們實際上並不關心用戶。實際上來說,這個流程並不奏效。因為Windows工程團隊中根本沒有人真正與用戶接觸過。他們實際上在傳遞著一位通用型用戶的理想化形象。 功能團隊就是根據這種占卜板式的模式進行諮詢的,接著又仔細地將所有空中樓閣式的想法全部合理化,然後就成為了一項決定。但這個決定終歸來說還是基於工程團隊的想法與創意,而非用戶的想法,這僅僅是因為用戶並沒有機會未出席這些會議。 為一款產品維持多個用戶界面是一項額外的工作,我們沒有足夠時間去測試多重配置。其他競爭者比我們擁有更多的市場份額,如果我們只是複制他們,可能我們能做得更好。所有我們說的這些內容都是真實的情況,所有這些都是支持最終決定的有力理由。但所有這些理由與論證均有微軟自問自答來完成。 在會議當天,項目管理會反復強調這項決定是多麼有利於用戶。他們會列舉一些事實來佐證這項決策:[color=Red]我們不想提供過多選項來讓用戶無從選擇;只有3%的人還在用那種方式,很明顯需要進行轉變了;一致性對微軟有利,所以也一定對用戶有利。每個人都面帶笑容,紛紛點頭同意這項決定並一致認為這是最佳決策。[/color]接著會議順利結束,這項功能有了新的發展方向。 雖然最終結果與當初構想的有些差距,也可能用戶體驗更差,但編寫軟件是需要妥協的嘛。這是一項可以接受的妥協,無論如何還不算太壞,也是最佳的選擇。如果真有用戶在現場,他們也會理解的。 以上就是我曾經作為Windows工程師時的所見所感。在看過那則視頻後,我突然間感覺自己又彷佛回到了那個會議室中。

source wmpu


COROLLA2003 2015-4-20 10:19



愛繼續留下,無愛默默轉身。 這是商業社會,只要能賺錢,我們這個1%和另外無數個1%在微軟眼裡都是一樣的。 當得不到更多份額的話,就算一直有1%的忠戶又有何用?

就像早前桑塔・納德拉的理念是移動為先,雲為先,所做出一個全平台通用的產品,各微軟應用開放涉佔各平台也令1%忠戶不接受。 但是,直到現時為止,這是成功的。 是忠戶固守還是微軟冒進? 留待時間證明吧。

source 3517277, XeonHo,


COROLLA2003 2015-4-26 19:39

[u][color=#003080]下一部手機還會是 Windows Phone 嗎] 投票成績揭曉:超過 60% 的讀者可能離開 Windows Phone 若 Windows 10 表現不如預期[/color][/u]



Regexman 2015-4-26 22:19

[quote]原帖由 [i]COROLLA2003[/i] 於 2015-4-26 07:39 PM 發表 [url=http://www.discuss.com.hk/redirect.php?goto=findpost&pid=415294590&ptid=24583389][img]http://www.discuss.com.hk/images/common/back.gif[/img][/url]
下一部手機還會是 Windows Phone 嗎] 投票成績揭曉:超過 60% 的讀者可能離開 Windows Phone 若 Windows 10 表現不如預期

http://blogjackphone.com/nokia/poll-result-60-wp-users-might-leave-wp-if-wi ... [/quote]
其實Metro UI行嘅方向係冇錯,理念正確而且前衛,但微軟依家竟然走回頭路,真係唔識講,希望Win 10仲有得改


*** 作者被禁止或刪除 內容自動屏蔽 ***

Regexman 2015-4-27 18:09

[quote]原帖由 [i]iamfire2[/i] 於 2015-4-27 04:03 PM 發表 [url=http://www.discuss.com.hk/redirect.php?goto=findpost&pid=415364962&ptid=24583389][img]http://www.discuss.com.hk/images/common/back.gif[/img][/url]
其實只係加多咗個"漢堡",其他Metro UI仲保留,只要細心用,就知道好多Metro UI系WP10既應用入面

如People hub基本無變

漢堡其實已經有遺Metro UI原則


*** 作者被禁止或刪除 內容自動屏蔽 ***

alanchu1996 2015-4-28 23:55

如果出左WP10 下年如果換機都想轉下 :loveliness:
由WP7到WP10 都一直進步緊 希望遲D可以追到ANDRIOD IOS

COROLLA2003 2015-4-30 05:46

Albert Shum responds to feedback on the Windows Mobile UI

The Windows Mobile UI has elicited a lot of feedback and concern from users in the past few weeks. While Microsoft has remained mum on this matter for a while, Albert Shum has finally shared his thoughts on the hamburger menu, pivots and circles vs squares.
Check out some choice quotes below for the gist of it and read the source link for the article in full.

On the Hamburger– “As with all UX design, it’s not the control that’s bad; it’s how it’s implemented. The right tool for the right job. The hamburger is often used as a consistent navigation element that’s the “home” for an app, always there, helping you go where you want to go. It’s less effective when the items listed in it don’t have a clear hierarchy, or when you need to access it frequently to accomplish your task. Sometimes the app bar, tabs, pivot, or a combination could be better controls for the job.

With our universal apps and adaptive UX we have an approach to design that lets developers build one app, but still tailor the UX to each device when it makes sense. We can use a hamburger icon without pivots on a PC version of the app for better keyboard and mouse navigation and then customize the same app to have pivots with swipe control for better one-hand-use on mobile. We’re making it possible for an app to have both hamburger and pivot controls—but to display the right control at the right time on the right device.”

On Commands at the bottom– “Without a doubt, the highest volume of dissatisfaction we’ve heard about Outlook Mail and Calendar for phones has been that people really like and really miss the Windows Phone 8 pattern of having most commands at the bottom of the screen, with an appbar that shows titles with the icons. We’re happy to let you know we’re not moving away from that pattern—the builds you’ve seen have an incomplete implementation of the “command bar” from Office and in the coming weeks you’ll see most of the commands back in a familiar-but-updated control at the bottom.”

On Squares vs Circles -“We’ve also heard that using circles to represent people doesn’t reflect our overall design and feels out of sync with what we’ve done in the past.

I’m going to segue a bit into some of our design thinking here, but stay with me for a bit….We did a lot of thinking about this during our planning stages for Windows 10, and what we tried to accomplish was to help the people in your life really stand out visually. This is particularly important in experiences like Start, and when you’re moving through different apps where there are people mixed with other content types. So for now, we’re going to stick with using circles to represent people, and we hope we’ll hear that you enjoy how easy it is to spot a friend when you’re glancing through all the things you do on your phone.”

It’s a pretty good read all things considered and helps shed some light on how Microsoft  responds to user feedback.

I’ve said a lot on this topic already and I will have some more in the future, for now let’s think Microsoft’s position -post heavy feedback of course – is exactly what the platform needs to evolve.

[img] http://wmpoweruser.com/wp-content/uploads/2015/04/Screenshot-193-e1430342806304.png [/img]

source wmpu


COROLLA2003 2015-5-1 06:28


Microsoft addresses the 'Hamburger menu' and other design decisions in Windows 10 for phones

Following its monumental Build 2015keynote earlier today, Microsoft has released a new blog post, penned by Operating Systems Group Design lead Albert Shum, going over some of the design decisions in Windows 10 for phones—even addressing the oh-so-controversial Hamburger menu.

Overall, the blog post touts Microsoft's adaptive approach to UI design in Windows 10. On the topic of that Hamburger menu, Shum points out that the menu works well as a "home" for an app but is less effective when it is used without an explicit purpose. However, this is where the adaptive design of Windows 10 comes in:

"With our universal apps and adaptive UX we have an approach to design that lets developers build one app, but still tailor the UX to each device when it makes sense. We can use a hamburger icon without pivots on a PC version of the app for better keyboard and mouse navigation and then customize the same app to have pivots with swipe control for better one-hand-use on mobile. We're making it possible for an app to have both hamburger and pivot controls—but to display the right control at the right time on the right device."

Shum also touches on another sore point with Insider users: the lack of commands at the bottom of the screen in Outlook Mail and Calendar for phones. The good news is they're not going away:

We're happy to let you know we're not moving away from that pattern—the builds you've seen have an incomplete implementation of the "command bar" from Office and in the coming weeks you'll see most of the commands back in a familiar-but-updated control at the bottom.

Similarly, Microsoft is listening to feedback about the placement of the address bar in the Edge browser(previously "Project Spartan"), and while they don't have anything to share yet, Shum says they are exploring different design options.

Here's a list of some of the other design decisions and upcoming changes Shum touches on in the post as well:

Photos: Menu icon in the PC app and pivots for phoneCalendar: Easier discovery for mini-month. Increased number of weeks shown in mini-month on larger devices. Week view in landscape.Mail: Unified inbox and Multi-Select coming in future updates.

Overall, the full blog post is a fascinating read for anyone interested in the design decisions going intoWindows 10, and we recommend checking it out in full.

Our own Daniel Rubino is heading into a Build sessions dedicated to this topic of Windows 10 design, so stay tuned for more on this hot top!

微軟詳解Windows 10 Phone UI設計決策&漢堡菜單方案

在今天的Build 2015首場主題演講結束後,微軟官方發布了一篇由操作系統組設計帶頭人Albert Shum撰寫的博客,Shum在文中詳細解釋了Windows 10 Phone的設計決策,當然也包括頗具爭議的漢堡菜單。 總的來說,這篇博客主要目的還是宣傳微軟在Windows 10 UI設計中執行的自適應式方案。在說到漢堡菜單時,Shum指出,當菜單作為一款應用的“家”時,它能很好勝任應用操作指令,但當其使用目的不明確時,所起的作用就大打折扣了。然而,這正是Windows 10自適應式設計的導入點:

有了我們的通用應用與自適應式UX(用戶體驗),我們為開發者提供了一種方法,使得他們能夠順利開發出一款應用,但仍需要根據每款設備來對UX進行修改以獲得良好的適配性。 我們可以在一個PC版應用中使用不搭載樞軸UI的漢堡菜單設計,這樣很好照顧了鍵鼠導航操作,然後還需針對同款應用的手機版本進行自定義,為其添加滑動式樞軸觸控手勢,以便於在單手操作的手機中使用。我們正在讓一款應用既配備漢堡菜單又配備樞軸控件,但會在正確的設備上及正確的時間上顯示正確的操控佈局。



同樣的,微軟也在傾聽用戶關於Edge瀏覽器(即之前的斯巴達瀏覽器)地址欄位置的反饋,但微軟還未就此項意見表態,Shum稱他們正在探索不同的設計方案。 下面是Shum談到的其他設計決策以及即將到來的UI新變化:

《照片》應用:PC 版採用漢堡菜單,手機版採用樞軸式設計《日曆》應用:更容易找到迷你月份,在大屏設備中增加迷你月份中的星期顯示數量。橫屏顯示星期視圖《郵件》應用:在以後的更新中統一收件箱與多選功能

不僅如此,微軟在Build大會上談到了Windws 10 Phone未來設計,雖說目前還只是概念設計,但微軟已經表示正在開發設計以及測試,詳情:《微軟展示未來的Windows 10 Phone UI新變化》。

source wc


COROLLA2003 2015-5-1 16:22

[u][color=#003080]Microsoft解釋Windows 10 手機版 App的設計概念,新的相片app將會取消漢堡包按鈕[/color][/u]


Regexman 2015-5-1 23:25

[quote]原帖由 [i]COROLLA2003[/i] 於 2015-5-1 04:22 PM 發表 [url=http://www.discuss.com.hk/redirect.php?goto=findpost&pid=415673835&ptid=24583389][img]http://www.discuss.com.hk/images/common/back.gif[/img][/url]
Microsoft解釋Windows 10 手機版 App的設計概念,新的相片app將會取消漢堡包按鈕

http://welovewp.hk/post24152 [/quote]
以前佢就係想用Touch套設計通殺,依家就係想用Mouse and keyboard套設計統一。好彩開始從回正軌,知道Touch同Desktop 設計要分開,如果唔係又死多獲
頁: [1] 2
查看完整版本: Windows 10 Phone 疑已確定採用漢堡菜單